crossing boundary between link's children makes click not follow link

NEW
Unassigned

Status

()

--
minor
15 years ago
8 years ago

People

(Reporter: jruderman, Unassigned)

Tracking

({testcase})

Trunk
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040423
Firefox/0.8.0+

Steps to reproduce:
1. Go to http://www.google.com/search?q=qwt
2. Mouse down on a link just to the left of a bold area.
3. Move the cursor right 1-2 pixels.
4. Mouse up.

Expected: follow the link, since 1-2 pixels is below the drag threshold.

Result: nothing happens.
(Reporter)

Comment 1

15 years ago
Created attachment 146965 [details]
testcase

This testcase uses a background color to make the element boundary easier to
see.
The issue here is simple. The mousedown happens on one node, the mouseup on
another.  So there is no click event, since the two parts of the click happen on
different nodes.  This is generally desirable, in fact.
(Reporter)

Comment 3

11 years ago
It's not what you want for link clicks, though...

Why doesn't a mouse down on one element and a mouse up on another cause an onclick event to fire targeted at the nearest common ancestor?
OS: Windows XP → All
Hardware: PC → All
Because generally you want to be able to cancel clicks by moving the mouse away before release... at least this is how most modern OSes behave.
(Reporter)

Comment 5

11 years ago
My proposal would not cause "moving the mouse away before release" to send onclick events to links or buttons.

Similar problems occur in bug 324396, "Middle-click that crosses focus outline does not close tab".
Assignee: events → nobody
QA Contact: ian → events
(Reporter)

Comment 6

8 years ago
I still see this bug on trunk.
(Reporter)

Updated

8 years ago
Duplicate of this bug: 324396
You need to log in before you can comment on or make changes to this bug.