DOM/prefixes: Difference between revisions
< DOM
(fill out prefixed apis with a few examples, policy, unprefixing, and dropping. float TOC) |
m (s) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div style="float:right">__TOC__</div> | |||
{{stub}} | {{stub}} | ||
Some [[DOM]] APIs have vendor prefixes on them. This page provides documentation on which (partial), why (Mozilla's DOM prefixing policy), and how we transition away from vendor prefixes. | Some [[DOM]] APIs have vendor prefixes on them. This page provides documentation on which (partial), why (Mozilla's DOM prefixing policy), and how we transition away from vendor prefixes. | ||
Latest revision as of 00:38, 16 August 2013
This article is a stub. You can help MozillaWiki by expanding it.
Some DOM APIs have vendor prefixes on them. This page provides documentation on which (partial), why (Mozilla's DOM prefixing policy), and how we transition away from vendor prefixes.
Prefixed APIs
element.mozMatchesSelectorwindow.mozAnimationStartTime- to be proposed in a standard?
window.mozRequestAnimationFrame- use window.requestAnimationFrame (FF23+, IE10+, Chrome)
- ... add any that you see on DevMo or anywhere else (e.g. the source code), link to where its defined/documented (e.g. DevMo link). Feel free to file a bug asking for any of them to be supported in unprefixed form (if not already), and link to the bug in the entry here.
Policy
In short: no new DOM/WebAPI prefixes.
Unprefixing
When do we implement an unprefixed version of an API?
Requirements for unprefixing a particular DOM API:
- There must be a public specification for the unprefixed version.
- We must make sure our implementation adheres to the specification before supporting the unprefixed version of an API in Gecko.
Dropping
When do we drop support for a prefixed version of an API?
Requirements:
- We must support an unprefixed version
- The web doesn't depend on the prefixed version too much (to be evaluated on a per case basis).