Chrome has incorrect event target in some situations
|Reported by:||filosofo||Owned by:|
|Component:||General||Keywords:||needs-patch needs-testing needs-isolating|
The result is that clicking a select element triggers a mouseover event on an element not in its ancestry. In the case of the WordPress admin, this means triggering the hover state on the admin bar (which reveals the dropdown sub-menu).
I can reproduce this in Chrome 8.0.552.224 on Linux but not Chrome 8.0.552.224 on Windows.
Attached is a page simplified to the bug's barest essentials. Change #some-element's position, top, or left CSS properties, and the bug does not occur. (The borders and positioning on the select element are just to make it clear that there's no overlap of the elements.)
I will report this upstream to Chrome. There are several options to prevent it from happening, but they're somewhat hacky. I'm going to see if I can come up with less-hacky solution before creating a patch.
Change History (22)
- Summary changed from Chrome on Linux Has Incorrect Event Target in Some Situations to Chrome has incorrect event target in some situations
- Milestone changed from Future Release to 3.3
- Priority changed from lowest to high
- Severity changed from trivial to blocker
- Milestone 3.2.2 deleted
- Resolution set to worksforme
- Status changed from new to closed