223638 - DOM Events in XUL documents incorrectly report at-target phase

Status: RESOLVED WORKSFORME

(Core :: XUL, defect)

Description

[Alex Vincent [:WeirdAl]]

For some reason, events going through XUL documents report they are in an
at-target phase while they are actually in a capturing phase.

Testcase coming up.

Comment 1

[Alex Vincent [:WeirdAl]]

Attachment: Testcase showing capturing phase reported as at-target phase

Testcase:  Open the attachment, and click on the button.

Expected results:
click(in count=1, target=button. currentTarget=#document)
click(in count=2, target=button. currentTarget=window element)
click(out count=1, target=button. currentTarget=window element)
click(out count=0, target=button. currentTarget=#document)
command(in count=1, target=button. currentTarget=#document)
command(in count=2, target=button. currentTarget=window element)
command(out count=1, target=button. currentTarget=window element)
command(out count=0, target=button. currentTarget=#document)

Actual results:
click(at-target count=0, target=button. currentTarget=#document)
click(at-target count=0, target=button. currentTarget=window element)
click(out count=-1, target=button. currentTarget=window element)
click(out count=-2, target=button. currentTarget=#document)
command(at-target count=-2, target=button. currentTarget=#document)
command(at-target count=-2, target=button. currentTarget=window element)
command(out count=-3, target=button. currentTarget=window element)
command(out count=-4, target=button. currentTarget=#document)

Comment 2

[Ronald Tilby]

This problem also is reproducible on Windows XP using Nightly 2003101604

Comment 3

[Alex Vincent [:WeirdAl]]

It's unclear when this happened, but Firefox 1.5.0.x now passes this testcase.  Yay!