Cut the mustard, recently a popular approach to managing progressive enhancement, means a page is placed in one of 3 states:
- full enhanced experience with scripts delivered and running
<noscript> for delivering a different experience to 3. It would be useful if this mechanism could be used to deliver a noscript experience to 2 too. (see e.g. https://github.com/Financial-Times/ft-origami/issues?utf8=✓&q=is%3Aissue+is%3Aclosed+ctm+noscript and https://github.com/Financial-Times/o-tracking/issues/83 for the hurdles jumped over to try to achieve a similar effect)
window.disableScripting(), which would only have an effect if some strict criteria were met (e.g. must be called in the first inline script within
I like this idea. I can imagine there might be some complexities around things like:
- What do you do if the
disableScripting() call is not the last statement in the block?
- What would be the effect on
<noscript> elements already encountered when parsing the page
Could it be easier to reload the page? So
disableScripting acts like a
window.reload() but when the page is reloaded it has JS disabled?
Content-Security-Policy: script-src 'none'
disableScripting or equivalent)