Closed
Bug 316235
Opened 19 years ago
Closed 14 years ago
use more generic mechanism for wrapper preservation
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 241518
Future
People
(Reporter: dbaron, Assigned: dbaron)
Details
Attachments
(1 file)
75.89 KB,
patch
|
Details | Diff | Splinter Review |
I'm splitting off using a more generic mechanism for wrapper preservation from the rest of the patch to bug 241518, for which a more generic mechanism is no longer useful. However, it would be useful for other things (e.g., wrapper preservation for any non-DOM-node objects); it's just a lower priority.
Assignee | ||
Comment 1•19 years ago
|
||
I'm sure this will bitrot quickly, but I may as well attach it.
Assignee | ||
Comment 2•19 years ago
|
||
The patch was against a tree with checkout start: Mon Nov 7 14:38:33 PST 2005, although my cvs mirror may not have been quite current at that time.
Assignee | ||
Comment 3•19 years ago
|
||
(Though I have to say, this patch should just work. Except for whether the Window Root stuff is right, it could probably just go in.)
Updated•15 years ago
|
QA Contact: ian → general
This is the only open bug with the APIchange keyword (there are 2 closed bugs, and I just removed it from a bug). I'm considering filing a bug to remove the keyword. (This bug hasn't had real activity since 2005, however it was touched twice since, so the modified date was going to be confusing anyway.)
Assignee | ||
Comment 5•14 years ago
|
||
In the end, this did land with bug 241518.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•