Re: [Edbrowse-dev] noscript

[Adam Thompson <arthompson1990@gmail.com>]

On Fri, Feb 21, 2014 at 04:41:17AM -0500, Karl Dahlke wrote:
> > 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.

Yeah, I forgot to say it'd be:
js
rf

rather than just:
rf

> 
> 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.

They appear on plenty of sites anyway if js doesn't run correctly.
I'm not sure how, probably by altering the contents of a particular tag if js
runs but initialising it with the non-js error,
or setting something to invisible in js.
> 
> 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.

In this case, what about for sites where you want js off but noscript on?  How about:
- add a flag saying if we want the noscript tags
- this is enabled by default in *all* cases where js is disabled
- have some way of disabling it for certain sites 
- also have a command to disable it globally which can then go in someone's init function

At the end of the day, my personal opinion is that noscript is (or certainly was) a suggested
mechanism for web developers to handle browsers without javascript support and
edbrowse should probably use this by default if it isn't going to try and run
the javascript.
However, as you say, in some cases these messages are just annoying and should
be switched off.  However, I think it should be a user's choice, particularly as there are cases where the web developers have actually used the noscript tags to do helpful things like provide non-js functionality.

Cheers,
Adam.