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
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.
A google search for this didn't seem to turn up anything useful. So i think we can mark it as [ChromeOnly] at least.
Should be fine to remove.
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #8491512 - Flags: review?(peterv) → review+
Target Milestone: --- → mozilla35
Status: ASSIGNED → RESOLVED
Last Resolved: 5 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? :)
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.