| Nemo_bis | |
| Feb 13 2013, 11:38 AM |
| F10531: file_44947.txt | |
| Nov 22 2014, 1:24 AM |
«Some preferences end with (requires JavaScript), but it is not consistently used, and given that practically everyone has javascript support these days, but a lot of people don't really know what it is, wouldn't it be better to remove the warnings?»
There are 6 such preferences in core.
Version: 1.21.x
Severity: minor
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Invalid | None | T40638 [DO NOT USE] Interface messages needing rewording or documentation and other issues with existing messages [superseded by #Voice_&_Tone] | ||
| Resolved | None | T46947 Remove "requires JavaScript" from preference texts | ||
| · · · |
Actually a lot of users JavaScipt isnt supported. Or in other cases especially on mobile browsers it causes inconsistencies (Lynx browser does not support JavaScript)
removing javascript keyword since it has nothing to do with JavaScript modifications.
Rahul: Thanks for the patch!
Betacommand: See comment 0 - it's not consistently used anyway.
(In reply to comment #7)
Rahul: Thanks for the patch!
Betacommand: See comment 0 - it's not consistently used anyway.
I would prefer us to err on the other side, then. What about adding those preferences items via Javascript? (only semi-joking)
Change 50614 had a related patch set uploaded by Siebrand:
(Bug 44947) Removed "requires JavaScript" from preference texts
Change 50614 merged by jenkins-bot:
Removed "requires JavaScript" from preference texts