From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] showscripts()
Date: Tue, 30 Jan 2018 10:41:58 -0500 [thread overview]
Message-ID: <20180030104158.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
The showscripts command, for debugging, only shows the scripts produced by html.
This is a problem as more and more scripts are created dynamically.
Pass in 1, or true, showscripts(1), to see all scripts under document.
These are gathered by getElementsByTagName("script");
The resulting list is left in document.scripts2,
so if you want to know more about script 4, access document.scripts2[4].
You can see the difference on most sites, example nasa; the second list is longer than the first, and indexes need not correspond.
Karl Dahlke
next reply other threads:[~2018-01-30 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:41 Karl Dahlke [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-19 2:38 Karl Dahlke
2017-09-19 17:58 ` Geoff McLane
2017-09-19 19:31 ` Karl Dahlke
2017-09-20 23:32 ` Geoff McLane
2017-09-20 23:56 ` Dominique Martinet
2017-09-23 23:40 ` Kevin Carhart
2017-09-20 23:59 ` Kevin Carhart
2017-09-21 1:56 ` Karl Dahlke
2017-09-20 13:38 ` Karl Dahlke
2017-09-21 0:33 ` Geoff McLane
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=20180030104158.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).