Page MenuHomePhabricator

Enable VisualEditor for all namespaces other than Project, Template, MediaWiki and Talk*
Closed, ResolvedPublic

Description

VE works well-enough for pages that aren't signed, except for ones where the pages rely on fiddly or partial wikitext munging, like the Template and MediaWiki namespaces. Consequently, we should be OK to enable VE in a larger number of namespaces, rather than just NS_MAIN and NS_USER:

  • NS_FILE
  • NS_HELP
  • NS_CATEGORY
  • wgContentNamespaces generally?

Part of the fun are things like the portal namespace which is defined per-wiki.

See also bug 55792 for comments about enabling VE in all namespaces, and why I think that's a bad idea.


Version: unspecified
Severity: enhancement

Details

Reference
bz55968

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:21 AM
bzimport set Reference to bz55968.

Change 90923 had a related patch set uploaded by Jforrester:
Enable VisualEditor for NS_FILE, NS_HELP, NS_CATEGORY

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

How well does VisualEditor handle the non-editable portions of File and Category pages? Do they just disappear when VE is invoked?

(In reply to comment #2)

How well does VisualEditor handle the non-editable portions of File and
Category pages? Do they just disappear when VE is invoked?

Those aren't on the page, they're just composited on in read mode. See for example https://www.mediawiki.org/wiki/Category:Requests_for_comment or https://www.mediawiki.org/wiki/File:2013-08-21_Flow_prototype.png to take two pages at random from MWwiki.