Closed Bug 395132 Opened 17 years ago Closed 17 years ago

DOMContentLoaded not fired at the result document

Categories

(Core :: XSLT, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 325891

People

(Reporter: aaronr, Assigned: aaronr)

Details

Attachments

(2 files)

Attached file xslt file
Looks like if you have a listener for DOMContentLoaded in the result document, it never gets notified after the XSLT is processed. There is a DOMContentLoaded event fired, though, because I see nsDocument::DispatchContentLoadedEvents getting called in the debugger. So that must be going to the source document. I talked with Jonas about this. He thinks that the event should go to the result document, not the source document. I'll own this for now. I'll create a patch when I get my next cycle of free time.
Attached file testcase
yep, its a dupe.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: