Bugzilla

It seems like `:hover` works a bit inconsistently in general on mobile (googling for "Android :hover" turns up a bunch of articles about it not doing what people expect). 

Testing in testcase 1 and the original site, it looks like we have some commonality and one minor behavior-difference that I think the screencast is demonstrating

In both Chrome and Firefox, when you touch the screen over a link (as in the case in this bug):
(A) If you move your finger **immediately** after you touch the screen, `:hover` state is never activated on the thing that you touched.
(B) If you don't move your finger (i.e. long-press), the `:hover` state gets activated and a context-menu appears for the link. (These happen at the same time in Firefox, vs. one-after-the-other in Chrome with a short delay between them.)

...BUT:
(C) If you wait a fraction of a second between touching & moving your finger. then Chrome activates the `:hover` state but does not show the context-menu for the link.

So it seems that in Chrome, adding-the-hover-state is decoupled (and happens slightly sooner) than showing-a-link-context-menu; whereas in Firefox, those two things happen atomically (with the hover state also being shown slightly later than in Chrome).

This probably merits a platform bug, but It doesn't look to me like this really breaks the site (or is an intended or particularly-discoverable way of viewing the preview images here); I'd rate this as very low-severity.  If you tap-and-hold the preview images, the preview shows up in both Firefox and Chrome (along with a context-menu, since you're long-pressing a link).

It seems like `:hover` works a bit inconsistently in general on mobile (googling for "Android :hover" turns up a bunch of articles about it not doing what people expect). 

Testing in testcase 1 and the original site, it looks like we have some commonality and one minor behavior-difference that I think the screencast is demonstrating

In both Chrome and Firefox, when you touch the screen over a link (as in the case in this bug):
(A) If you move your finger **immediately** after you touch the screen, `:hover` state is never activated on the thing that you touched.
(B) If you don't move your finger (i.e. long-press), the `:hover` state gets activated and a context-menu appears for the link. (These happen at the same time in Firefox, vs. one-after-the-other in Chrome with a short delay between them.)

...BUT:
(C) If you wait a fraction of a second between touching & moving your finger. then Chrome activates the `:hover` state but does not show the context-menu for the link.

So it seems that in Chrome, adding-the-hover-state is decoupled (and happens slightly sooner) than showing-a-link-context-menu; whereas in Firefox, those two things happen atomically (with the hover state also being shown slightly later than in Chrome).

This probably merits a platform bug to investigate whether there are good reasons to decouple these events in the way that Chrome does; but it doesn't look to me like this really breaks this particular site (or is an intended or particularly-discoverable way of viewing the preview images here); I'd rate this as very low-severity.  If you tap-and-hold the preview images, the preview shows up in both Firefox and Chrome (along with a context-menu, since you're long-pressing a link).