Whitespace within == == headers is not insignificant.
It should be, as this makes it harder to use the DoEditSectionLink hook to add more inline elements after or before the heading (they will display slightly differently depending on whether ==Heading== or == Heading == was used).
(This isn't visible when using Tidy, as Wikimedia sites do, as it strips the spaces. It can be seen in the resulting HTML on Tidy-less wikis, though.)
Version: 1.21.x
Severity: trivial
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T28751 Extensions that should really be core functionality (tracking) | |||
| Resolved | matmarex | T47051 Phase out the Vector extension; merge the good parts into core (tracking) | |||
| Open | None | T50719 Issues related to section editing (tracking) | |||
| Open | Feature | None | T2156 Add section edit link for 0th section of a page/article | ||
| Resolved | matmarex | T43729 Tidy up and deploy Vector's sectionEditLinks (move section edit links next to headers) | |||
| Resolved | matmarex | T47803 Whitespace between == == headers should be insignificant |
Hrm, the spaces should be insignificant *in* the HTML output. What exactly are the differences you're seeing?
== Headline == and ==Headline== should always yield <h3><span class="mw-headline" id="Headline">Headline</span></h3>, and never <h3><span class="mw-headline" id="Headline"> Headline </span></h3> (note the spaces).
Also see the parser tests changes on the patch for a more precise description :)
Yeah, but those spaces shouldn't cause any rendering difference... but maybe they do. Meh. :D
Related URL: https://gerrit.wikimedia.org/r/59620 (Gerrit Change I6a51e3ee07fe7622b9c708c78563795d7a1118fc)