3 ms·
The current title, "Firefox Is Going to Support Chrome Extensions", is neither the headline nor the subject of the page; Chrome isn't mentioned. The title is si
by hackuser 11y ago
The current title, "Firefox Is Going to Support Chrome Extensions", is neither the headline nor the subject of the page; Chrome isn't mentioned. The title is simply "WebExtensions" and it's Mozilla's wiki page on the subject.
"WebExtensions documentation" would be accurate and informative.
- tree_of_item 11y agoChrome is mentioned many times on that page: > Namespacing > At this time, all APIs are accessible through the chrome.* namespace. When we begin to add our own APIs, we expect to add them to the browser.* namespace. Developers will be able to use feature detection to determine if an API is available in browser.*. > See https://developer.chrome.com/extensions/manifest https://developer.chrome.com/extensions/manifest for a complete list of manifest directives. Of these, we currently support the following:
- hackuser 11y agoSearching the page for "Chrome" returns 3 results. One is a namespace's name, another is part of a URL, and the third is a short mention of a planned feature for Chrome. While I was technically wrong, I think my point stands.