In T388696#10649903, @matmarex wrote:

In T220751#10605294, @Od1n wrote:

I don't remember if "raw headings" are counted in the &section=N indexes. If they are not counted, that's good news for the case at hand: provided we are fine with targetting h1 ... h6 levels, we could replace everything with just .find( '.mw-heading' ) (and it wouldn't even need the subsequent .filter()).

I tried this suggestion from the other ticket, and it seems to work. Even without code changes, just setting $wgMFMobileFormatterOptions['headings'] = [ '.mw-heading' ] apparently works. @Jdlrobson-WMF You may need to do some QA testing to verify different cases, but maybe you can avoid having to make code changes.

Thanks for this suggestion @matmarex

The change you propose does seem to address the page issues bug, but only because it corrects logic in MobileFrontend's PageHTMLParser which was never updated when we introduced $wgParserEnableLegacyHeadingDOM (it still refers to the legacy HTML!)

The reason the change you proposed works is that this variable is passed down to mw.config as mw.config.get( 'wgMFMobileFormatterHeadings') which is used by the PageHTMLParser

I'd rather not alter the behaviour of MakeSectionsTransform.

I think a good next step would be to rewrite these tests for the new parser and drop support for the old version of heading markup as proposed in T390245: Simplify MobileFrontend's PageHTMLParser to support less content modes and then re-evaluate this ticket.