User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; fi-fi) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fi; rv:220.127.116.11) Gecko/20100316 Firefox/3.6.2
A div with text, when you mouse down on the text and mouse up outside the text, no click event is fired, even though the event targets are the same for mousedown and mouseup.
The same surprising behaviour happens in Safari as well.
Created attachment 436452 [details]
Example of the problem
This would seem to be related to: https://bugzilla.mozilla.org/show_bug.cgi?id=326851 . The difference is that no visible parent-child-relationship is needed, but the problem occurs with a div with text content as well.
This is possibly the behavior we need to keep for backward compatibility.
I'll bring this up on WebApps WG / DOM 3 Events.
And the behavior doesn't seem too surprising.
When text is clicked, user clicks actually a text node, and then releasing
happens on the div element.
Thanks for the response!
In practice, this problem shows up with, for example, links that have been styled like buttons by adding padding and background to them. When the user mousedowns on the link text but mouseups in the padded area, the event does not fire. For the user, the button feels like randomly working and not working, since even a small movement of the mouse while clicking the link might prevent the click event.
Ok, per current DOM 3 Events draft the click event should be fired.
I'll change this and hopefully the change doesn't cause too many regressions.
Created attachment 449318 [details] [diff] [review]
I pushed the patch to tryserver.
If everything looks good there, I'll write the tests and ask reviews.
Created attachment 449341 [details] [diff] [review]
This may break something on the web, so would be great to get this in
Oops, I need to remember to land this.
Will do later today.
This was landed in: http://hg.mozilla.org/mozilla-central/rev/c9c2ad1bf872