In Firefox OS in the following demo: http://jsbin.com/jofov 1.) Press and hold any button to observe the highlighted :active state 2.) Slide your finger away from the button and continue observing the highlighted :active state 3.) Release your finger on a *different* button Result: View the 'Clicked: XXX' on-screen message for the button you released your finger on Expected: The :active state should disappear as soon as your finger *leaves* the bounds of the button the touch started on and therefore NO 'click' event should be observed

Build Info for Comment 0: Gaia 4f352142a54f7f7ae2c460aad9049eda4b0edb14 Gecko https://hg.mozilla.org/mozilla-central/rev/9ac3e2dd0898 BuildID 20140508160203 Version 32.0a1

See also: Bug 1013378 - Subsequent taps after first one do not trigger :active state

(In reply to Justin D'Arcangelo [:justindarc] from comment #0) > Expected: The :active state should disappear as soon as your finger *leaves* > the bounds of the button the touch started on FWIW this is not what happens on desktop, which is why I'm making this bug depend on the UX spec in bug 1009684.

(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #3) > (In reply to Justin D'Arcangelo [:justindarc] from comment #0) > > Expected: The :active state should disappear as soon as your finger *leaves* > > the bounds of the button the touch started on > > FWIW this is not what happens on desktop, which is why I'm making this bug > depend on the UX spec in bug 1009684. However, the 'click' event doesn't trigger on desktop when you move the pointer over to another element in mid-click.

Agreed. If this bug was just about that then it would just be a simple bug.

Just to be clear, in this case, the dependency on bug 1009684 means this bug is not actionable until that bug is resolved.

Never got the promised UX spec, and now it's too late.