Closed Bug 1245140 Opened 4 years ago Closed 2 years ago
Get addons to stop using DOM
We need this to be able to do bug 1207321, right?
So https://mxr.mozilla.org/addons/search?string=DOM_OBJECT&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=addons says "Found 492 matching lines in 215 files". A bunch of those are fxos emulators which we can ignore. for the rest, it would be good to figure out whether they would actually break if we made this flag a no-op (and possibly stopped exposing XPCWrappedNative to the web)...
It looks like some of them are just using code from old tutorials, like: http://web.archive.org/web/20090221185408/http://xulplanet.com/tutorials/xulqa/q_treebview.html What exactly does an object gain by setting this flag? Would there be a workaround available for cases where an add-on breaks? Also, would it be possible to add a deprecation console warning to give developers time to adjust?
Peter, do you know what the current state of the answers to Jorge's first two questions is? If no, I can try to figure it out. For the third question, it should be possible to a deprecation warning, yes.
I guess this counts as an issue that will go away when XPCOM addons are no longer supported.
Depends on: 1448414
Is this WFM now?
Yep, effectively; there's no more DOM_OBJECT flag. I just forgot to resolve this bug, even after adding the note to self in comment 6...
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.