This was changed in T37247: content-holding <div> should only contain the page text for the MW parser but no task was created for the other parser, whoops.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Add mw-parser-output class to Parsoid's output | mediawiki/services/parsoid | master | +5 -1 |
Event Timeline
Tim mentioned this last Thu when we were syncing up .. I was planning to take a look soon, but thanks for the ticket!
This was changed in T37247: content-holding <div> should only contain the page text for the MW parser but no task was created for the other parser, whoops.
To be fair, I did ask (in T37247#3181097 and on wikitech-l) for people who know about how the Parsoid ecosystem works to say whether that would be necessary or desirable, but no one replied.
It was on my list for a face-to-face discussion in Vienna as to whether this was a good idea…
Change 352711 had a related patch set uploaded (by Subramanya Sastry; owner: Subramanya Sastry):
[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output
Change 352711 merged by jenkins-bot:
[mediawiki/services/parsoid@master] Add mw-parser-output class to Parsoid's output