I thought about this potential case afterwards. Need to test. It's likely not very high priority because you have to turn WTE on for your account in preferences, and WTE doesn't work without JS.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Move NWE URL changes into JS | Alex Monk | mediawiki/extensions/VisualEditor | master | +10 -30 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T132023 VisualEditor support for editing inside CollaborationKit | |||
| Open | Feature | None | T138636 Allow using VisualEditor on Special:MassMessage | ||
| Open | None | T138642 VisualEditor should provide a clean integrated VE/WT editor widget that can be integrated into any context | |||
| Resolved | None | T130400 (Actually) Add wikitext support for citoid for automatic reference insertion | |||
| Open | None | T90864 "Publish changes" button poorly discoverable for VisualEditor users switching to classic (wikitext) editor | |||
| Open | None | T171974 Improve and consolidate our unified editing platform so that it's great on all devices | |||
| Resolved | None | T104479 Provide a modern wikitext editor ("2017 wikitext editor") | |||
| Resolved | • AlexMonk-WMF | T148077 If you have NWE enabled, on a non-JS machine (or disabled) you can't edit |
Event Timeline
Comment Actions
If you're a non-JS user you won't be able to switch on the beta feature, but of course people have different machines so could theoretically enable on one and try to use on another. And of course users occasionally lose JS due to network issues or whatever.
Comment Actions
Should we just be doing all the URL rewriting in the client then? Or introducing a third tab and hiding in with CSS, like ve-edit?
Comment Actions
Change 320318 had a related patch set uploaded (by Alex Monk):
Move NWE URL changes into JS