Closed
Bug 1317596
Opened 9 years ago
Closed 9 years ago
Stop using LegacyIsCallerChromeOrNativeCode in geolocation code
Categories
(Core :: DOM: Geolocation, defect)
Core
DOM: Geolocation
Tracking
()
RESOLVED
FIXED
mozilla53
| Tracking | Status | |
|---|---|---|
| firefox53 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
10.66 KB,
patch
|
jdm
:
review+
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → bzbarsky
|
|
Assignee | |
Updated•9 years ago
|
Summary: Stop using IsCallerChromeOrNativeCode in geolocation code → Stop using LegacyIsCallerChromeOrNativeCode in geolocation code
|
|
Assignee | |
Comment 1•9 years ago
|
||
Attachment #8810722 -
Flags: review?(josh)
|
||
Updated•9 years ago
|
Attachment #8810722 -
Flags: review?(josh) → review+
|
|
||
Comment 2•9 years ago
|
||
Actually, please hold off landing this until I can verify addon usage, since the DXR addon search is busted right now.
|
|
Assignee | |
Comment 3•9 years ago
|
||
I don't mind holding off, but what did you want to verify? There should be no script-observable behavior changes.
Flags: needinfo?(josh)
|
|
||
Comment 4•9 years ago
|
||
Disregard that, I didn't notice that nsIDOMGeoGeolocation isn't scriptable.
Flags: needinfo?(josh)
Pushed by bzbarsky@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/683874fa09af
Stop using LegacyIsCallerChromeOrNativeCode in geolocation code. r=jdm
|
||
Comment 6•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in
before you can comment on or make changes to this bug.
Description
•