Page MenuHomePhabricator

Provide the VE wikitext editing mode as the mobile wikitext editor
Open, LowPublic40 Estimated Story Points

Event Timeline

Change 333491 had a related patch set uploaded (by Jforrester; owner: Esanders):
[mediawiki/extensions/MobileFrontend] [WIP] Enable VE's new wikitext mode in MobileFrontend

https://gerrit.wikimedia.org/r/333491

Change 434731 had a related patch set uploaded (by DLynch; owner: DLynch):
[mediawiki/skins/MinervaNeue@master] [WIP] NWE

https://gerrit.wikimedia.org/r/434731

Change 434730 had a related patch set uploaded (by DLynch; owner: DLynch):
[mediawiki/extensions/MobileFrontend@master] [WIP] Use NWE if available

https://gerrit.wikimedia.org/r/434730

I wound up doing more on this, at the hackathon. (Admittedly, not having seen Ed's patch, otherwise I'd have added to it instead.)

This will probably become easier to finish up after T198765 is done and all this code will be in one repo.

Related to this, we should make publish flow connected to the upcoming edit card release T225725 so that there aren't two different versions of that final edit summary page depending on if you’re coming from VE or Wikitext editing.

@matmarex Maybe you can merge those two editors on mobile? The source editor on mobile doesn't have many features, but 2017 wikitext editor does. There should not be any problem copying those features.

Change 333491 had a related patch set uploaded (by Esanders; owner: Esanders):
[mediawiki/extensions/MobileFrontend@master] Enable VE's new wikitext mode in MobileFrontend

https://gerrit.wikimedia.org/r/333491

Change 434730 abandoned by Jdlrobson:
[mediawiki/extensions/MobileFrontend@master] [WIP] Use NWE if available

Reason:
Given its age and lack of recent activity I'm going to assume this is inactive now. Please restore with update if that's not the case. Thanks!

https://gerrit.wikimedia.org/r/434730

Change 434731 abandoned by Esanders:

[mediawiki/skins/MinervaNeue@master] [WIP] NWE

Reason:

There's no editor code in minerva anymore

https://gerrit.wikimedia.org/r/434731

Change 434730 restored by Esanders:

[mediawiki/extensions/MobileFrontend@master] [WIP] Use NWE if available

https://gerrit.wikimedia.org/r/434730

Note that there is an explicit consensus against VisualEditor's wikitext mode (NWE) at EnWiki, and I expect other wikis would agree. I would recommend simply closing this task, unless someone wants to open a discussion with the community to see if new&different consensus is possible.

That discussion looks like it's specifically about the desktop wikitext editor, and this task is only about the entirely-separate mobile editor. The arguments being made are certainly focused on that environment, anyway.

Mind you, said consensus probably should get revisited even for desktop. The preview objection is largely irrelevant now because parsoid-HTML is being rolled out for article views (and is also fairly irrelevant on mobile because it does previews differently anyway). Load time has presumably improved somewhat in the five years since that proposal, even if only because of hardware improvements (and, again, mobile heavily pushes you into section editing, which would avoid the long-article performance issues even if there were no changes at all). 🤷🏻

Change 434730 merged by jenkins-bot:

[mediawiki/extensions/MobileFrontend@master] Support VisualEditor's wikitext mode

https://gerrit.wikimedia.org/r/434730

The new mobile wikitext mode is not enabled for anyone on any wiki yet. We haven't decided how, when or if we want to roll it out.

Yes, this patch just adds a site-config called MFEnableVEWikitextEditor that can be set to true to turn it on for a wiki.

@matmarex @DLynch

IMPORTANT REMINDER: English Wikipedia has a standing consensus against VE's wikitext mode, and it's highly likely other wikis will come to the same result if it looks like the project is starting up again. The Foundation should have preformed a full evaluation at that point on whether to formally terminate the project, and it would be unwise to work towards rolling it out or activating it without consulting the community.