Once [ChromeOnly] is supported on dictionary members, we can uncomment its use on MutationObserverInit.animations and remove the explicit chrome-caller check in nsDOMMutationObserver::Observe.
This still needs to happen, right?
yes. ::Observer method has currently ThreadsafeIsCallerChrome check for this.
Created attachment 8759300 [details] [diff] [review] patch I was lazy and put also the check for animation part to that test.
Assignee: nobody → bugs
FWIW, getObservingInfo is [ChromeOnly] method
Comment on attachment 8759300 [details] [diff] [review] patch r=me
Attachment #8759300 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/009d5a56af0f use [ChromeOnly] on MutationObserverInit, r=bz
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox49: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in before you can comment on or make changes to this bug.