Item11120: If JavaScript is required (anywhere) , the user should be notified.

I recently encountered a problem in saving a page, because I had JavaScript turned off (my bad, I know :-/). Specifically, when I tried to save, I got the strikeone page. When I clicked OK, I was sent back to the original (unedited) task. I found this behavior quite mystifying and frustrating.

IMNSHO, if JavaScript is required for ANY action, the user should be notified. Silent failure violates Principle of Least Astonishment, etc.

-- RichMorin - 11 Sep 2011

It appears that this has been partially addressed in the upcoming 1.1.4. The strikeone dialog now reports that the requested action will not be permitted. However this may be too late for a user who has done a lot of edits and is unable to save. So it would still be preferable to warn the user on the edit page.

-- GeorgeClark - 11 Sep 2011

Indeed it would. At the least, documentation should make it clear the increasingly important role that Javascript plays.

Regraded from Normal to Enhancement, and Confirmed.

-- CrawfordCurrie - 13 Oct 2011

I did a partial fix - committed to PatternSkin on trunk, just for the editor page but have not merged to 1.1.4. It uses messages.tmpl as a common message template. However I'm concerned that I'm abusing this file. It's previous purpose was just for oops messages. Is it okay to expand the use for other messages that appear in multiple locations?

-- GeorgeClark - 13 Oct 2011

I recently ran into this problem again, using Google Chrome and the NotScripts extension. In that case, I would have expected the extension to complain, as well...

-- RichMorin - 07 Dec 2011

The fix to this no longer applies, and NatEdit on Foswiki 1.2 rather clearly non-functional when javascript is disabled. We really ought to just have a banner indicating that Javascript is required.

-- GeorgeClark - 12 Jan 2015

Commenting is disabled while not logged in