Closed Bug 234722 Opened 22 years ago Closed 22 years ago

Should nodes removed from the DOM during an event still trigger their default action?

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bzbarsky, Assigned: chofmann)

Details

It seems that our "testing radar" seems to be utterly unable to deal with bugs that are not yet completely fixed but have had a partial patch checked in, so bug 232798 has been resolved. This is the followup for the original issue raised in that bug. Please reassign this to the default DOM owner after moving over the relevant information from that bug, the patch, and the review requests.
OS: Linux → All
Hardware: PC → All
Summary: Should anchor nodes removed from the DOM during a click event still trigger? → Should <a href=""> elements removed from the DOM during a click event still trigger their default action?
There are other types of anchors than <a href> (eg xlink, <area>, etc).
Summary: Should <a href=""> elements removed from the DOM during a click event still trigger their default action? → Should anchor nodes removed from the DOM during a click event still trigger their default action?
Well I suppose this really applies to all nodes and all events, not just clicks on link events.
Summary: Should anchor nodes removed from the DOM during a click event still trigger their default action? → Should nodes removed from the DOM during an event still trigger their default action?
Sure.
Doesn't the DOM Events spec specifically state that changes to the DOM tree during event dispatch does *not* in any way impact the event processing? IOW, whatever you do to the DOM tree from an event handler, it in no way changes how the event propagates, and so on. Or did I miss the point here?
Hmm.. yeah, I guess that applies here.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.