Jonas just suggested to me that we could implement nsISupportsWeakReference on content nodes, and I wanted to file a bug on it so we don't forget. This seems like something that could be useful. Jonas suggested doing it using: * a tearoff that implements nsISupportsWeakReference * a weak reference object (not nsWeakReference) that holds on to the nsIContent (or nsINode) pointer directly rather than the tearoff, which could go away * [I'm filling in this part; he didn't mention it] the content's pointer to the weak reference would presumably be in its Slots Then again, if it became *too* useful, this might not be the best implementation strategy. But it could always be revisited.

So what would be the use case where this is be needed. (I guess it is not too difficult to come up with several use cases ;))

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.