Tapping or text selection near a link does not take zooming into account

UNCONFIRMED
Unassigned

Status

()

Firefox for Android
General
UNCONFIRMED
3 years ago
2 years ago

People

(Reporter: Nicolae Albu, Unassigned)

Tracking

39 Branch
ARM
Android
Points:
---

Firefox Tracking Flags

(fennec+)

Details

(URL)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150525141253

Steps to reproduce:

Scenario 1:
1. Go to a page that has a link and something "clickable" next to it that is not a <a href> or a button. For example, a <div> or an image with handlers.
2. Zoom in to the maximum so touching the clickable item with the finger does not reach the link.
3. Tap on the clickable item.

Scenario 2:
1. Go to a page that has a link and some text next to it.
2. Zoom in to the maximum so touching the text with the finger does not reach the link.
3. Tap and hold on the text with the intention of copying the text.


Actual results:

Scenario 1:
The link is triggered instead of the clickable item, although there is a distance of like 1 cm between where I tapped and the link. I recorded the behavior here: https://youtu.be/bk2kMNXHDL8 .

Scenario 2:
The tap and hold is triggered on the link (opening the link context menu) instead of the text (selecting the text). I will upload a video of this too if it helps.


Expected results:

Scenario 1:
The clickable item should have been triggered instead of the link.

Scenario 2:
The text should have been selected instead of opening the context menu of the nearby link.

The feature that triggers links when tapping near them should take zooming into account. In my video, I tapped something that was over 1 cm further from the link and the link was triggered.
(Reporter)

Updated

3 years ago
OS: Unspecified → Android
Hardware: Unspecified → ARM
Snorp, any idea what's going on here?
Flags: needinfo?(snorp)
(Reporter)

Comment 2

3 years ago
I think the "tap near link / button helper" uses page pixels / points (at scale 1) instead of display pixels (when zooming, the distance in pixels is way larger).
This results in a big usability problem. This problem is encountered even on a 10 inch tablet, where the distance between the finger and the link / button is ridiculously large...
tracking-fennec: --- → ?
Let's reevaluate this one after native APZ has landed.
tracking-fennec: ? → +
Flags: needinfo?(snorp) → needinfo?(rbarker)

Comment 4

3 years ago
¡Hola Nicolae!

Is this still a problem on Nightly from https://nightly.mozilla.org/ ?

AFAIK the "native APZ" mentions has landed recently.

¡Gracias!
Flags: needinfo?(nicolae_albu2004)
(Reporter)

Comment 5

3 years ago
Yes, still a problem on today's nightly...
Do I have to enable something in about:config?
Flags: needinfo?(nicolae_albu2004)
(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #3)
> Let's reevaluate this one after native APZ has landed.

I went to the page in the youtube video and was unable to reproduce the issue in nightly.
Flags: needinfo?(rbarker)
(Reporter)

Comment 7

2 years ago
I'll try again using latest nightly.
(Reporter)

Comment 8

2 years ago
It's way better (meaning usable at all vs unusable) in nightly than in stable, though it still doesn't compare with other browsers.
In Firefox I still need a large amount of zoom to prevent activating the link from above the button.
In Opera, for example, I don't need to zoom at all.
(In reply to Nicolae Albu from comment #8)
> It's way better (meaning usable at all vs unusable) in nightly than in
> stable, though it still doesn't compare with other browsers.
> In Firefox I still need a large amount of zoom to prevent activating the
> link from above the button.
> In Opera, for example, I don't need to zoom at all.

I think this and Bug 1233272 are probably the same issue. We definitely seem to have a hit test issue when links are close to selectable non-links. This may have been by design but the current implementation feels too aggressive in favoring links over other selectable items.
You need to log in before you can comment on or make changes to this bug.