On Mon, Dec 16, 2013 at 7:01 PM, Andrea Giammarchi
<andrea.giammarchi at gmail.com> wrote:
> We are all use to write abominations such `var url = window.webkitURL ||
> windows.mozURL || windows.URL` and similar stuff all over, the reason
> utilities libraries are often preferred, so while I am very happy that IE
> team finally has been able to catch up and be even in front of other
> browsers, I do believe that incomplete specifications or those still under
> discussion should be adopted with prefixes until finalized in their form in
> order to promote less mistakes in the long term.

That way you end up with e.g. having to support mozMatchesSelector()
forever in addition to matches(). We're certainly going to avoid doing
that in Gecko.

If you're unclear on the name, just make it clear in the specification
that the name is not stable and that therefore it cannot ship yet (you
could implement it and ship it in nightlies and such of course).


-- 
http://annevankesteren.nl/

On Mon, Dec 16, 2013 at 7:01 PM, Andrea Giammarchi <andrea.giammarchi at gmail.com> wrote:
> We are all use to write abominations such `var url = window.webkitURL ||
> windows.mozURL || windows.URL` and similar stuff all over, the reason
> utilities libraries are often preferred, so while I am very happy that IE
> team finally has been able to catch up and be even in front of other
> browsers, I do believe that incomplete specifications or those still under
> discussion should be adopted with prefixes until finalized in their form in
> order to promote less mistakes in the long term.

That way you end up with e.g. having to support mozMatchesSelector()
forever in addition to matches(). We're certainly going to avoid doing
that in Gecko.

If you're unclear on the name, just make it clear in the specification
that the name is not stable and that therefore it cannot ship yet (you
could implement it and ship it in nightlies and such of course).