From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] home runs (fwd)
Date: Sun, 20 May 2018 22:24:56 -0400 [thread overview]
Message-ID: <20180420222456.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1805201822580.26234@carhart.net>
All corect. Just not sure what piece of javascript is not running, that would do what you did manually.
I can't find any reference to those particular nodes anywhere.
So it's looping through in some other way, maybe the whole document I don't know, and finding them and turning them on,
but it's not working for us which is weird as there are no errors.
I tried changing the user agent to look like a commercial browser, no dice.
Well it's not our highest priority, since I can type hover and bring everything back in,
or better still, run without js, which isn't needed here,
but it just nags at me a bit.
next prev parent reply other threads:[~2018-05-21 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 1:37 Kevin Carhart
2018-05-21 2:24 ` Karl Dahlke [this message]
2018-05-21 9:50 ` Kevin Carhart
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=20180420222456.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).