From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] noscript
Date: Fri, 21 Feb 2014 07:46:47 -0500 [thread overview]
Message-ID: <20140121074647.eklhad@comcast.net> (raw)
Ok - the noscript tags become active when js is not.
As Adam points out, this should be the default.
We can talk about features to turn them off in the nojs directive in the
config file later.
Yes I too have run into some sites where it claims js is off, but
it is really on.
My objects are not complete enough for it to recognize that it is on,
so it prints those warning messages.
These are the sites that lead us to the objects
or methods that we are missing.
But that's another story.
My jsrt file includes some noscript tags for testing.
Browse it with js off and you'll see what I mean.
I put in some tags, not just text, to make sure the html runs
inside noscript, as it should.
Karl Dahlke
next reply other threads:[~2014-02-21 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 12:46 Karl Dahlke [this message]
2014-02-21 18:59 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 9:41 Karl Dahlke
2014-02-21 12:05 ` Adam Thompson
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=20140121074647.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).