https://en.wikipedia.org/w/index.php?title=Wikipedia:Non-free_content_criteria&oldid=1019877704
[[:en:w:WP:NFCC]] section headings are rendered as plain text including the equals signs. (app only, not web)
2.7.50373-beta-2021-09-07
Description
Description
Event Timeline
Comment Actions
Parsoid will not support arbitrary string / token gluing to generate other tokens.
This edit introduced that and as the description notes, it is a hacky way. A better fix would be to embed the full heading into the noinclude/includeonly directives.
So <noinclude>==Foo==</noinclude><includeonly>===Foo===</inlcudeonly> and so on. So, editing the page with this would be the right fix for this.
Comment Actions
is it not valid to want parity between parsers? if Parsoid can't move one way then move mw core the other way?
Comment Actions
the section headings now appear in app out of order. (and one section is empty with no content)
Comment Actions
We are slowly moving towards Parsoid being used for all use cases. For now, some of these edge cases aren't worth trying to fix always since they fall out of the internal design (which are different in both).
Comment Actions
the section headings now appear in app out of order. (and one section is empty with no content)
This probably merits a separate bug report since this is no longer from Parsoid (or markup) but further up the stack - needs investigation as to where exactly. @Dbrant @MSantos @Jgiannelos FYI.