From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] :before :after
Date: Wed, 21 Feb 2018 19:00:06 -0500 [thread overview]
Message-ID: <20180121190006.eklhad@comcast.net> (raw)
In-Reply-To: <20180221230751.5orqxzkaixf5y5th@toaster>
> is it possible to only apply *these* selectors and quickly skim over the
> rest and do the on-demand stuff for them?
Well you're thinking exactly as I.
I did some stats, and 280 out of 5000 selectors in stackoverflow are of the before after type.
Applying 280, rather than 5000, is probably feasible.
And remember, stackoverflow is almost certainly a worst case.
Other sites don't have 5000 selectors, or 280 injecting selectors.
I laid some groundwork, wherein these selectors are flagged as generating text.
cssList[i].gentext = true;
Still I may want to optimize the way these selectors are applied.
Maybe some of the hashing code that I wrote, then decided I didn't need and threw away,
but it's still in github if I want it.
Karl Dahlke
prev parent reply other threads:[~2018-02-21 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 11:56 Karl Dahlke
2018-02-21 23:07 ` Adam Thompson
2018-02-22 0:00 ` Karl Dahlke [this message]
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=20180121190006.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).