The Editing-team suggested that the wikis listed in T329407 which are fully opted-in to DiscussionTools would be good "next steps" targets for Parsoid-read-views-for-Discussion-Tools deployment:
We should conduct visual diff testing on these (restricted to the Talk namespace) to sanity check that they are appropriate; talk to the community; and then hopefully turn on Parsoid for the Talk namespace for these wikis.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Release | None | T84936 Release VisualEditor-MediaWiki as "1.0" | ||
| Open | None | T50429 [Epic] Support editing parts of a page in VisualEditor-MediaWiki | |||
| Open | None | T54365 Explore performance gains from progressive (JIT?) de-alienation in VisualEditor | |||
| Open | None | T174303 Copy-pasting linked ISBN numbers from view mode HTML into VisualEditor inserts wikitext links to Special:BookSources (it should turn them into magic links?) | |||
| Open | Feature | None | T54091 The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces | ||
| Open | None | T55784 [EPIC] Use Parsoid HTML for all page views | |||
| Open | None | T272987 [EPIC] Parsoid read views for DiscussionTools | |||
| Open | None | T360903 Parsoid DiscussionTools for arwiki/cswiki/huwiki (phase 2) |
While odd namespace number was a good proxy on Wikitech, Wikipedias use __NEWSECTIONLINK__ a lot, which may lead to inconsistent behavior on them. Maybe it should be reevaluated whether DiscussionTools can be used to determine which parser to use by default.