Obsolete
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.
Allows web sites to register themselves as possible handlers for content of a particular MIME type.
Note: Web sites may only register content handlers for themselves. For security reasons, it's not possible for an extension or web site to register content handlers targeting other sites.
Syntax
navigator.registerContentHandler(mimeType, uri, title);
mimeTypeis the desired MIME type as a string.uriis the URI to the handler as a string.titleis the title of the handler presented to the user as a string.
Example
navigator.registerContentHandler(
"application/vnd.mozilla.maybe.feed",
"http://www.example.tld/?foo=%s",
"My Feed Reader"
);
Notes
For Firefox 2 and above, only the application/vnd.mozilla.maybe.feed, application/atom+xml, and application/rss+xml MIME types are supported. All values have the same effect, and the registered handler will receive feeds in all Atom and RSS versions (see bug 391286).
Firefox is the only browser that implemented this feature, and it wasn't implemented to match the standard. This feature has since been removed from the HTML standard and shouldn't be used.
Specifications
| Specification | Status | Comment |
|---|---|---|
| HTML 5.2 The definition of 'registerContentHandler()' in that specification. |
Recommendation | This feature is present in HTML 5.2, but has since been removed from the WHATWG HTML Living Standard. |
Browser compatibility
The compatibility table on this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
See also
- Web-based protocol handlers
Navigator.registerProtocolHandler()- XPCOM Interface Reference > nsIWebContentHandlerRegistrar > registerContentHandler - This shows how to use this function XPCOM scope