Fire UserDataHandler for removed nodes

RESOLVED WONTFIX

Status

()

Core
General
RESOLVED WONTFIX
8 years ago
8 years ago

People

(Reporter: Brett Zamir, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: 

I see that when using the DOM's setUserData() UserDataHandler's, all of the events work, except for NODE_RENAMED (since renameNode() is not yet supported) and NODE_DELETED. I'm attaching a simple test case (you can ignore the first 'if' block which just demonstrates other browsers can be made to support NODE_DELETED (in JavaScript)). I see that Bug 337541 was marked as WONTFIX and BugĀ 324871 removed that support, but I'd hope there'd be some way to fix it so NODE_DELETED did trigger.

Since this information isn't otherwise readily serializable (as it would be adding namespaced attributes or the like), it's convenient to be able to trigger these user data handlers.

Thanks...

Reproducible: Always
(Reporter)

Comment 1

8 years ago
Created attachment 430516 [details]
Demonstrates lack of NODE_DELETED support and workaround but only for some non-Mozilla browsers
I believe the decision on NODE_DELETED is that we have no plans to implement it.
Yeah, the problem is that it's too hard to implement interoperably due to being too dependent on GC behavior.
Right, see bug 324871, comment 17.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.