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] noscript
Date: Fri, 21 Feb 2014 04:41:17 -0500	[thread overview]
Message-ID: <20140121044117.eklhad@comcast.net> (raw)

> However I think displaying the contents of the noscript tags if js is already
> dead makes sense, since if we have a js failure,
> it'd then be possible to refresh the page to get the noscript contents.

When you refresh the page you "quit" the old page.
That frees the js context.
Then the new page gets a new js context and js is working again.
It would then likely run into the same error.
You have to specifically turn off js first, then refresh.
But yes you could do that.

I can't help wonder if this feature would be annoying,
there are lots of sites like Google that I run all the time without js,
it saves time and errors and the site runs just as well.

nojs = partner.googleadservices.com
nojs = google.com
nojs = googlesyndication.com
nojs = google-analytics.com

Do I really want to read all those noscript messages every time?

Your browser is not javascript enabled.
This site will not perform optimally under these conditions.
To access all the features of this site, please turn on javascript.
Here are directions on how to do so.
Blah Blah blah for each browser.

Do I really want to read through that every time I access Google,
or any other site that I have determines runs fine without javascript?
I'm not trying to be contrary here, just thinking of
all the ramifications of turning noscript on.
Or maybe noscript runs if js is dead,
but not for the nojs commands in the config file,
because I have already determined it's ok to run those sites without js.

Karl Dahlke

             reply	other threads:[~2014-02-21  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  9:41 Karl Dahlke [this message]
2014-02-21 12:05 ` Adam Thompson
2014-02-21 12:46 Karl Dahlke
2014-02-21 18:59 ` 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=20140121044117.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).