@Jdlrobson See Channel Tunnel §Passenger traffic volumes (mobile). On desktop (Vector), when moving the mouse over the blue [A] in the table header, there is no popup displaying the link. However, there is one for each of [84] and [85]. Similarly, on mobile, when [A] is clicked, the black box at the bottom displays the loading image.

I don't think this is too likely to be fixed, because the templates rely purely on CSS classes and anchors and there's already an obvious alternative for them (using normal inline <ref>…</ref> tags like everyone has since 2006). However, they are useful in some cases, for instance in relatively small tables where many items share the same footnotes and <references/> would produce "1. ^ a b c d e f g h i j k l m n o p q r …" before the actual note text.

No problem :)

As an aside, I wonder if this might have anything to do with adding section link/anchor support for Hovercards/Page-Previews (which is probably necessary for it to work on Wiktionary). I can't find any reported bugs though.

At the very least, to take away from this issue, is the fact that very likely there is incorrect error handling in the mobile popups. It shouldn't be possible that the popups gets stuck in an infinite spinner loop :)

Change 352614 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
[mediawiki/extensions/MobileFrontend@master] False references should fall back to hash change

https://gerrit.wikimedia.org/r/352614

There are comments on rEMFRd076963b63ad: False references should fall back to hash change from both myself and @bmansurov.

@bmansurov and @phuedx new patch is up.

I've left a couple of questions in the patch.

All answered.

Change 352614 merged by jenkins-bot:
[mediawiki/extensions/MobileFrontend@master] Not-existent references should fall back to hash change

https://gerrit.wikimedia.org/r/352614

@Jdlrobson: Are there any pages on the Beta Cluster that @ABorbaWMF could use to test this?

Nope. A general QA of clicking references and checking their functionality would probably be more useful at this point given all the changes to the code. @ABorbaWMF please be sure to check in stable and beta.

@Jdlrobson, I took a look at this on beta and production. On beta, I used the Dog article, and the reference links worked fine. On production, I used the Channel Tunnel article from the original description, and the reference links worked except for the [A] reference link.

Here is what I found: if the user loads the page and taps the [A] reference link before tapping any other reference, the endless spinner appears. If the user taps another reference link first, then taps the [A] reference link, the link works just fine.

I tried on a few android and apple devices (mobile and tablet), they all displayed the same behavior. I also tested some other pages on production, and all the reference links worked well. The Channel Tunnel article is the only one I have seen with this behavior.

It doesn't work when tapped after another reference (at least from the links above); it just retains the text from the reference which was tapped before it.

The patch that fixes the bug on production will be in the next deploy. It is only fixed on the beta cluster.

Imported https://en.m.wikipedia.beta.wmflabs.org/wiki/Channel_Tunnel
So you can verify there.

Works as expected; thanks for importing the page.

Just noticed: On desktop, after the footnote has been clicked, clicking any normal reference now automatically scrolls to the fake footnote. This also seems to happen if the page URL has a section link. Does this also happen on normal mobile devices?

@Jc86035 eh. please be more descriptive, to avoid people making incorrect interpretations of your report.. Which link, which skin, the exact links you are clicking. Are you reporting an additional issue (please file a separate ticket), or are you saying that the validation that has been done on pre-production was incorrect...

@TheDJ On the beta.wmflabs.org link above (Firefox, desktop), I clicked the [A] link, clicked the caret to go back to [A], and then clicked reference 9. The page scrolled back to [A], although the popup displayed. (I think this also happened on my phone earlier with a section link.) I'll file a separate ticket.

I can reproduce. This is problematic. The onShowDrawer has "$window.one( 'click.drawer', $.proxy( self, 'hide' ) )" which for some reasons immediately triggers the hide() on the drawer (something like event handlers not being synchronised due to the earlier cancellation of the window I suspect....)

I also found another problem where, when you click the [ or ] of a reference you get an error, because onClickReference() assumes that you clicked the link, not the surrounding brackets

        $dest = $( ev.target ),
	href = $dest.attr( 'href' );

^^ ev.target will be text node '[ '. filed as T166548: Clicking [ or ] surrounding a reference throws an error when trying to present the reference drawer

The bug I filed is here: T166544

@Jdlrobson - has this been deployed yet? I'm still not seeing in in production (look ok on the beta cluster)