22527 - [EVENTTARG] absolutely positioned checkbox doesn't respond to mouse events

Status: VERIFIED DUPLICATE of bug 13213

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Nick Meara]

Overview Description:

A checkbox form control that is situated away from other elements using css
absolute positioning does not respond to mouse events.

Steps to Reproduce:

The URL above shows an example of the problem.

Actual Results:

The control is positioned correctly, but does not respond to mouse events.
Keyboard events (<Tab> to select and <Space> to toggle) work after the page has
been clicked.

Expected Results:

The control is positioned correctly and responds to appropriate mouse and
keyboard events.

Build Date and Platform:

Build 1999122208 on Mac OS 8.6

Additional Builds and Platforms:

Build 199122208 on Win NT 4

Comment 1

[Hixie (not reading bugmail)]

Migrating from {css2} to css2 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...

Comment 2

[Marc Attinasi]

Attachment: Refinement of the HTML referenced in the URL field...

Comment 3

[Marc Attinasi]

When the checkbox is positioned to the left too far (using negative values for 
the 'left' style) mouse events are not dispatched and the control is not 
responsive. If the control is visible it should probably be responsive.

Comment 4

[Pierre Saslawsky]

Changing platform/OS to All.

Comment 5

[Pierre Saslawsky]

Reassigned to attinasi

Comment 6

[Marc Attinasi]

I don't know if this is a duplicate of 12232 or not: it seems similar but I'll 
let you decide. Either way, it looks like an event-targeting bug where the 
control is outside of the parent-block's bounds.

Comment 7

[joki (gone)]

Accepting, not a dupe of 12232.  May be dbaron's bug.

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think this is a duplicate of bug 13213.  See my comments on that bug for why I
think the problem remains even with my changes.

Comment 9

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This has the same problem with children extending outside the views.  Something
in the view code needs to change, and it's the same problem as bug 13213. 
Marking as duplicate.

*** This bug has been marked as a duplicate of 13213 ***

Comment 10

[Sebastian Späth]

VERIFY duplicate