For the record, this bug happens because:
- webbrowser-app’s long-tap detection is implemented in JS as a userscript, using a combination of event handlers for touchstart and touchend events and a timer
- 8tracks (and apparently other webapps, see bug #1287749) swallow the touchend event
Note that when we switch to oxide, we can use the 'contextmenu' event (which on touch is triggered on long tap) instead of implementing a custom long-tap detection mechanism. This means we will not be affected by webapps swallowing the touchend event any longer, i.e. this bug will automagically be fixed.
For the record, this bug happens because:
- webbrowser-app’s long-tap detection is implemented in JS as a userscript, using a combination of event handlers for touchstart and touchend events and a timer
- 8tracks (and apparently other webapps, see bug #1287749) swallow the touchend event
Note that when we switch to oxide, we can use the 'contextmenu' event (which on touch is triggered on long tap) instead of implementing a custom long-tap detection mechanism. This means we will not be affected by webapps swallowing the touchend event any longer, i.e. this bug will automagically be fixed.