Closed
Bug 1066826
Opened 9 years ago
Closed 9 years ago
Remove Navigator::MozisLocallyAvailable API
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla35
People
(Reporter: tanvi, Assigned: bzbarsky)
Details
(Keywords: addon-compat, dev-doc-complete)
Attachments
(1 file)
5.52 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
It doesn't look like this is called anywhere in gecko code: http://mxr.mozilla.org/mozilla-central/source/dom/base/Navigator.cpp#896 It is in an idl so it may or may not cause addon compatibility issues if we remove it: http://mxr.mozilla.org/mozilla-central/source/dom/webidl/Navigator.webidl#259
![]() |
Assignee | |
Comment 1•9 years ago
|
||
So more precisely: 1) This is callable by web content, but restricted to same-origin URIs. And totally not standardized. 2) There is precisely one extension I see in the addons mxr that uses it. We should either remove it entirely or make it chromeonly if we think that extension is important.
Flags: needinfo?(jorge)
Flags: needinfo?(jonas)
A google search for this didn't seem to turn up anything useful. So i think we can mark it as [ChromeOnly] at least.
Flags: needinfo?(jonas)
![]() |
Assignee | |
Comment 4•9 years ago
|
||
Attachment #8491512 -
Flags: review?(peterv)
![]() |
Assignee | |
Updated•9 years ago
|
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Updated•9 years ago
|
Attachment #8491512 -
Flags: review?(peterv) → review+
![]() |
Assignee | |
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/e8b6a242343d
Keywords: dev-doc-needed
Target Milestone: --- → mozilla35
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/e8b6a242343d
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
I don't have major objections against this being removed (I trust that you did it for a reason). But for the record, we've found this very useful when doing preloading of image resources. Images that may or may not already be in the users cache (using this method to test before we fire off a background prefetch). I had also opened an issue in Chromium about this: https://code.google.com/p/chromium/issues/detail?id=179934 Their response: "This would ideally be a more common standard, and would probably need an async API to be acceptable." Perhaps we were the only user of this api? :)
Comment 8•9 years ago
|
||
Release notes: https://developer.mozilla.org/en-US/Firefox/Releases/35#Interfaces.2FAPIs.2FDOM Reference updated: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/mozIsLocallyAvailable
Keywords: dev-doc-needed → dev-doc-complete
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•