Change Details

Brought to my attention by @Sdkb in T386758 (thank you!) Looks like this was broken during fixes to Parsoid in T359005 **Steps to replicate the issue** (include links if applicable): * Visit https://en.m.wikipedia.org/w/index.php?title=PayScale&direction=prev&oldid=1276323293&useparsoid=0 * Scroll down to overview * Click the issues banner **What happens?**: Banner doesn't open **What should have happened instead?**: * Banner should open * No warnings in JS console {F58426981,size=full} Note: it does seem to work in Parsoid. **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): All browsers e.g. Browser stack Android Galaxy S23 Chrome **Other information** (browser name/version, screenshots, etc.): There are also some deprecation warnings that may be related

Brought to my attention by @Sdkb in T386758 (thank you!) Looks like this was broken during fixes to Parsoid in T359005 **Steps to replicate the issue** (include links if applicable): * Visit https://en.m.wikipedia.org/w/index.php?title=PayScale&direction=prev&oldid=1276323293&useparsoid=0 * Scroll down to overview * Click the issues banner **What happens?**: Banner doesn't open **What should have happened instead?**: * Banner should open * No warnings in JS console {F58426981,size=full} Note: it does seem to work in Parsoid. **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): All browsers e.g. Browser stack Android Galaxy S23 Chrome **Other information** (browser name/version, screenshots, etc.): There are also some deprecation warnings that may be related == Requirement Investigate why the page issues banner does not function on mobile using the legacy parser and determine the root cause for it not opening. The banner should be interactive without causing console errors. == BDD ``` Feature: Investigate non-functioning page issues banner on mobile legacy parser Scenario: Page issues banner opens correctly on legacy parser Given I visit the PayScale article with useparsoid=0 on mobile When I scroll to the Overview section and click the issues banner Then the banner should open And no warnings should appear in the JavaScript console ``` == Test Steps Test Case 1: Verify page issues banner opens on mobile legacy parser 1. Visit PayScale article with legacy parser. 2. Scroll down to the Overview section. 3. Click the page issues banner. 4. AC1: Confirm the banner opens and displays the issue details. 5. Open the JavaScript console. 6. AC2: Confirm there are no warnings or errors in the console.

Brought to my attention by @Sdkb in T386758 (thank you!) Looks like this was broken during fixes to Parsoid in T359005 **Steps to replicate the issue** (include links if applicable): * Visit https://en.m.wikipedia.org/w/index.php?title=PayScale&direction=prev&oldid=1276323293&useparsoid=0 * Scroll down to overview * Click the issues banner **What happens?**: Banner doesn't open **What should have happened instead?**: * Banner should open * No warnings in JS console {F58426981,size=full} Note: it does seem to work in Parsoid. **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): All browsers e.g. Browser stack Android Galaxy S23 Chrome **Other information** (browser name/version, screenshots, etc.): There are also some deprecation warnings that may be related == Requirement Investigate why the page issues banner does not function on mobile using the legacy parser and determine the root cause for it not opening. The banner should be interactive without causing console errors. == BDD ``` Feature: Investigate non-functioning page issues banner on mobile legacy parser Scenario: Page issues banner opens correctly on legacy parser Given I visit the PayScale article with useparsoid=0 on mobile When I scroll to the Overview section and click the issues banner Then the banner should open And no warnings should appear in the JavaScript console ``` == Test Steps Test Case 1: Verify page issues banner opens on mobile legacy parser 1. Visit PayScale article with legacy parser. 2. Scroll down to the Overview section. 3. Click the page issues banner. 4. AC1: Confirm the banner opens and displays the issue details. 5. Open the JavaScript console. 6. AC2: Confirm there are no warnings or errors in the console.