I'm seeing this again at https://en.m.wikipedia.org/wiki/Surtsey .

Has this patch been deployed to Wikipedia? I'm still seeing the incorrect behaviour there.

I'm not sure why T164916 was marked as duplicate, but since it was, here's more info on it:

Android 6.0.1, Chrome 58.

Please consider the case of "page issues" that pertain to a section rather than the whole article. We don't want them losing their context or, even worse, getting lost entirely.

This also affects nowiki tags: see this thread on the Wikipedia village pump.

'This page has some issues' only appears for amboxes in the lead section. Some are intended for use in other sections; these are completely hidden on mobile, which is problematic for content-dispute templates such as {{Original research}}, which are important for informing readers that what they're reading is not necessarily up to Wikipedia's usual standards. These templates also can't be replaced by a "page component", unless it can be attached to a specific section, since by their nature they don't pertain to the article as a whole.

@Jdlrobson Wikipedia does indeed work again. Thanks! As a side effect, I'm also seeing seeing usage hints and the first image repeated at the top of the page, and search suggestions are also showing wikidata descriptions - I've seen some of these before but none immediately before the breakage iirc.

In T114599#1707492, @Jdlrobson wrote:

Were you still able to interact with the menu icon in the top left corner? Did clicking that work without loading an entire new page?

In T114599#1700811, @Jesant13 wrote:

In T114599#1700297, @MZMcBride wrote:

This sounds like a JavaScript issue of some kind. Are you able to look at Chrome's error console?

I don't know if that's possible to do through Google Chrome on Android. I looked around but didn't see an option.

Update: Chrome and Naked Browser are now broken too. I guess I had old styles and scripts cached or something.

Chrome (and other WebKit browsers such as Naked Browser), as well as Opera, are unaffected for me, but Firefox (version 41 on Android 5.1, Motorola Moto X) exhibits this behaviour.