Closed Bug 1372584 Opened 8 years ago Closed 8 years ago

Click event does not provide an alert

Categories

(Core :: DOM: Events, defect)

53 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: irena.kull, Unassigned)

Details

Attachments

(1 file)

Attached file FFClickEventIssue.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce: Run attached file. • Click into the outer black DIV -> you will get a corresponding alert • Click into the inner red DIV -> you will get the corresponding alert from the inner red DIV and from the outer black DIV • Now press the mouse button within the inner red DIV hold it, move it out of the inner red DIV into the outer black DIV and release the mouse button there -> Actual results: there is no alert from the outer DIV Expected results: The alert should be raised as in other browsers, e.g. Chrome, Edge.
Component: Untriaged → DOM: Events
Product: Firefox → Core
Reading Example #8 of https://www.w3.org/TR/uievents/#click, it says ".... .... this will likely still trigger a click event ... ...". Does that imply our current behaviour does not disobey the spec? I wonder if this behaviour is well defined in the spec.
Flags: needinfo?(sshih)
We stop dispatching a click event when user mouse down and up on different elements.
Flags: needinfo?(sshih)
(In reply to Ming-Chou Shih [:stone] from comment #2) > We stop dispatching a click event when user mouse down and up on different > elements. Does that mean this bug is invalid or do we need to revise our code to be compatible?
Flags: needinfo?(sshih)
Bug 1089326 is related to this.
oops, that was wrong bug.
(In reply to Hsin-Yi Tsai (55 Regression Engineering support) [:hsinyi] from comment #3) > (In reply to Ming-Chou Shih [:stone] from comment #2) > > We stop dispatching a click event when user mouse down and up on different > > elements. > > Does that mean this bug is invalid or do we need to revise our code to be > compatible? I don't see the necessity to fire a click in this case. I mean do users really want a click when mouse down and up on different elements? I'd prefer to change it as invalid.
Flags: needinfo?(sshih)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Please consider the behavior of other browsers, like IE, Chrome, Edge. They all fire the click. Thanks, Irena
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: