Closed Bug 41428 Opened 22 years ago Closed 3 years ago
XBL prototype chain must support forking
When bindings are used with differing base classes, the prototype chain between the object and the binding whose base class differs must be dynamically forked or everything will go to hell really fast. This is a critical XBL problem. Probably not nsbeta2, but we can't ship with this.
Whiteboard: nsbeta3- → [xbl1.0], nsbeta3-
Target Milestone: --- → M18
mass-moving xbl1.0 bugs to future, adding helpwanted keyword
Target Milestone: M18 → Future
Target Milestone: Future → mozilla0.9
back to the future
Target Milestone: mozilla0.9 → Future
Nominating for mozilla1.0. This needs to be targeted at a nearer milestone than Future before too long. /be
David - could you give us a pointer as to how difficult this would be to fix or where to start looking? It would be really nice to have this fixed for the SVG implementation, so that we don't have to duplicate tons of xbl code for every single svg-element.
Can anybody confirm the relation to Bug 190970, please? Or am I just to dump?
This is a mass change. Every comment has "assigned-to-new" in it. I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.