Closed Bug 1324035 Opened 3 years ago Closed 3 years ago

Stop using ThreadSafeIsCallerChrome in nsMimeTypeArray and nsPluginArray

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla53
Tracking Status
firefox53 --- fixed

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

(Blocks 1 open bug)

Details

Attachments

(4 files)

Use CallerType instead.
Blocks: 1324044
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #8819362 - Flags: review?(kyle) → review+
Attachment #8819364 - Flags: review?(kyle) → review+
Attachment #8819365 - Flags: review?(kyle) → review+
Attachment #8819366 - Flags: review?(kyle) → review+
Pushed by bzbarsky@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/108b378e3508
part 1.  Fix codegen to pass a CallerType to Length() calls that are generated for indexed getters if the indexed getter itself needs a CallerType.  r=qdot
https://hg.mozilla.org/integration/mozilla-inbound/rev/2507af1c9c82
part 2.  Stop using nsContentUtils::ThreadSafeIsCallerChrome in nsMimeTypeArray.  r=qdot
https://hg.mozilla.org/integration/mozilla-inbound/rev/414b97796bb7
part 3.  Stop using nsContentUtils::ThreadSafeIsCallerChrome in nsPluginArray.  r=qdot
https://hg.mozilla.org/integration/mozilla-inbound/rev/13f20e14bb7e
part 4.  Change nsContentUtils::ResistFingerprinting to just take a dom::CallerType instead of having all its consumers check it.  r=qdot
Depends on: 1316616
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.