From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] css in C
Date: Mon, 26 Feb 2018 14:44:02 -0500 [thread overview]
Message-ID: <20180126144402.eklhad@comcast.net> (raw)
Well there you have it, 2000 lines of code.
It's so fast you can't even measure it, even for stackoverflow.com, 5000 selectors and 5000 nodes.
Course that may be because it isn't working properly.
It only makes 157 assignments, which seems awfully small.
Or maybe most of those selectors are for situations that don't come up,
i.e. a selector for every conceivable situation.
It will take a long time to actually debug this mess.
dbcss can help in this regard, dumps lots of information to /tmp/css
As a simple spotcheck,
ok(document.body.style) has all sorts of attributes, as one would expect.
Karl Dahlke
next reply other threads:[~2018-02-26 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 19:44 Karl Dahlke [this message]
2018-02-27 9:33 ` Kevin Carhart
2018-02-27 11:24 ` Karl Dahlke
2018-02-28 0:31 ` Kevin Carhart
-- strict thread matches above, loose matches on Subject: below --
2018-02-24 19:21 [Edbrowse-dev] css in c Karl Dahlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180126144402.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).