New revisions (all types: post, summary, header) will be created as wikitext. Migrating existing revisions is not within the scope of this task.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
API: Make format parameters always default to 'fixed-html' | mediawiki/extensions/Flow | master | +8 -27 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • DannyH | T171977 Annual Plan 2017-2018, Audiences 5: Increase current editor retention and engagement | |||
Resolved | • DannyH | T171982 Annual Plan 2017-2018, Audiences 5, Goal 3: Provide better workflow and communication experiences | |||
Open | None | T167928 Improve structured discussion features for the communities that use them, based on user feedback and prioritising technical debt | |||
Open | None | T335843 Purge all old html version code from Parsoid repo once we switch VE from RESTBase to ParserCache | |||
Open | None | T174372 Store content as wikitext, not HTML | |||
Open | None | T174374 Use a mixed storage format, setting the system to slowly migrate over from HTML to wikitext storage | |||
Declined | Trizek-WMF | T178390 Support Structured discussion storage format change | |||
Declined | BUG REPORT | None | T93457 Babel templates do not render correctly in posts and boards provided by StructuredDiscussions | ||
Open | None | T93838 Add CSS modules that Parsoid tells us are relevant |
Event Timeline
Change 387810 had a related patch set uploaded (by Catrope; owner: Catrope):
[mediawiki/extensions/Flow@master] API: Make format parameters always default to 'fixed-html'
Change 387810 merged by jenkins-bot:
[mediawiki/extensions/Flow@master] API: Make format parameters always default to 'fixed-html'
No, this is not yet resolved. With my fix, this "works" now, but would be a performance disaster. We need to implement caching for the rendered HTML, probably using the parser cache in a bastardized way (because what we're caching is Parsoid HTML instead of Parser.php HTML, and doesn't correspond 1:1 to a page or revision). I've been meaning to work on this, but it got buried under a variety of other things.
Given the recent change of focus, do we want to keep this on the board?
@Catrope: from your last comment, it doesn't look like this is nearly done or that you are actively working on it.
Growth-Team discussed in triage this week, we won't have time to work on this in the near-to-medium term.