> 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 _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
