Closed Bug 1317597 Opened 3 years ago Closed 3 years ago
Get rid of Legacy
Is Caller Chrome Or Native Code use in ns Object Loading Content
It dates back to before webidl bindings, when we exposed random XPCOM stuff to the web.
These checks date back to when we didn't have webidl bindings and could end up exposing random XPCOM methods to the web. That doesn't happen anymore.
Attachment #8810725 - Flags: review?(kyle)
Attachment #8810725 - Flags: review?(kyle) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/b26a22e74be4 Stop using LegacyIsCallerChromeOrNativeCode use in nsObjectLoadingContent. r=qdot
You need to log in before you can comment on or make changes to this bug.