edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] stackoverflow and css
Date: Sun, 11 Feb 2018 16:24:46 -0500	[thread overview]
Message-ID: <20180111162446.eklhad@comcast.net> (raw)
In-Reply-To: <20180211194301.gx6i6nago4ietkxo@toaster>

If you put

nojs = js-sec.indexww.com

in your config file then stackoverflow browses; we have excised the js with the infinite loop.
Once browsed, I can drop into jdb and list out all the selectors in cssList.
There are 3198 of them.
I have put them on my website for your review.

www.eklhad.net/csslist

Almost all of them specify node.class, and would benefit from the hashing mechanism described in my previous email.

Karl Dahlke

  parent reply	other threads:[~2018-02-11 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 18:53 Karl Dahlke
2018-02-11 19:25 ` Adam Thompson
2018-02-11 19:43   ` Adam Thompson
2018-02-11 21:03     ` Karl Dahlke
2018-02-11 21:24     ` Karl Dahlke [this message]
2018-02-13 19:05       ` Adam Thompson
2018-02-11 23:08     ` 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=20180111162446.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).