Navigator.registerContentHandler()

Deprecated

This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

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);
  • mimeType is the desired MIME type as a string.
  • uri is the URI to the handler as a string.
  • title is 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

BCD tables only load in the browser

See also