Fire mousemove events on long press

NEW
Unassigned

Status

()

Firefox for Android
General
P4
normal
6 years ago
9 months ago

People

(Reporter: heycam, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [lang=js])

(Reporter)

Description

6 years ago
It used to be possible with Fennec XUL to hover on elements on the page by doing a quick "tap and hold" but releasing before the context menu popped up.  I think it might have done this by moving the (invisible) mouse pointer to that position.  This was helpful for some sites where content is available only on mouseover.  This doesn't seem to be possible on Fennec Native.

I don't know if "tap and hold but less for 1 second" is really the right interaction to use, since it's a bit tricky and unobvious, but it at least worked for me.
Priority: -- → P4
Duplicate of this bug: 778426
See Also: → bug 951377

Comment 2

4 years ago
So I guess this is similar to bug 756942 and is what https://support.mozilla.org/en-US/questions/977027 and https://support.mozilla.org/en-US/questions/930854 are complaining about.

Personally it's killing me, I can't use a (private) page without this. On KitKat (4.4.2) both the stock Chrome browser and Dolphin handle this perfectly: a long tap triggers both the link menu *AND* the hover event. You can then dismiss the link menu and use whatever the hover event enabled.

On Firefox you get either the link menu (long tap) or hover AND link activation (short tap), and then you have to race the page load. I haven't managed to win that race even once.
Good idea. We can do that.
Whiteboard: [mentor=wesj][lang=js]
Summary: not possible to hover on elements in a page → Fire mousemove events on long press
(Assignee)

Updated

4 years ago
Mentor: wjohnston@mozilla.com
Whiteboard: [mentor=wesj][lang=js] → [lang=js]

Comment 4

2 years ago
Actually, another (better?) way would be to pop up the context menu and activate hover at the same time, then allow to leave context menu using back arrow, but leave hover activated.

That's how both Android's built-in browser, and Ubuntu Touch's browser handle it.


However, an even better approach would be to not fire a click event on a tap which changes the hover state of an element. That way, a first tap on such an element hovers it, and a second tap follows the link (if element is a link)

Elements which don't have a :hover style would still be clickable on first tap
Mentor: wjohnston2000@gmail.com
You need to log in before you can comment on or make changes to this bug.