On 2015-07-16 1:05 AM, Karl Dubost wrote:
Hello,
(mostly for people of DOM and CSS)

tl;dr: A list of unprefixed properties where the prefixed version has been 
dropped.

Context:

A feature has 4 states (or at least my impression):

1. No support
2. prefixed only support (MozFoo and -moz-bar)
3. prefixed and unprefixed support (MozFoo, Foo, -moz-bar and bar)
4. unprefixed only support (Foo and bar)

For Web Compatibility, dropping the unprefixed version may create issues (See 
the recent issue with -moz-gradient).

I would love to know if we have an "always up to date" list features state for 
Firefox/Gecko. Both caniuse and MDN are giving the information on when the prefixless 
version has been introduced but never when/if the prefix has been dropped.

I'm not aware of one.  I think the answer is no.

Why is it interesting?

Given the current state of the Chinese and Japanese Web, some prefixes seem 
impossible to drop both for Mozilla, but also other browser vendors. Having the 
list of the current state could help us to send the right message to Web 
developers on
    1. adding prefixless versions to their code
    2. sometimes to remove the prefixed version of their code (more difficult 
because of old mobile devices).

I think it's probably easier if you provided a list of the CSS properties and DOM APIs that we can't unprefix because of compat concerns, and made the right people aware of that. Given that we have decided to not use prefixes any more, it doesn't seem necessary to try to solve this problem in the general case.

PS: I want to know that for WebKit, Blink and Edge too. I will ask around.

In my experience, for WebKit, the Apple documentation is pretty accurate, and again AFAIK they never remove prefixed APIs. For Blink, https://www.chromestatus.com/features#prefix has a few entries. For Edge, I can't find something similar on https://status.modern.ie/...
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to