3 ms·

I hope I will not see many more of this kind of news. Dear browser makers, please, enable your prefixed CSS properties only in dev/night/beta builds. Leave onl

by gioele 14y ago

I hope I will not see many more of this kind of news. Dear browser makers, please, enable your prefixed CSS properties only in dev/night/beta builds. Leave only unprefixed CSS properties in the release stable browsers. With this you will be able to test new features, show them to web developers and, at the same time, save them from the madness of maintaining five different slightly different versions of new CSS properties. How many developers do you think will not remove the `-moz-` prefixes from they CSS? Who do you expect to say "from now on we will only support Firefox 16, let's drop the prefixed version used by older versions"? Prefixes are for testing, not for stable applications.

mbrubeck 14y ago
That's exactly what Firefox developers like Henri Sivonen [1] and David Baron [2] think, and their proposals have a lot of support within Mozilla and a high chance of being adopted. It would be great to get other vendors on board too. [1] http://hsivonen.iki.fi/vendor-prefixes/ http://hsivonen.iki.fi/vendor-prefixes/ (see "Keep Experimental Features in Experimental Builds") [2] https://groups.google.com/d/msg/mozilla.dev.platform/itl6mtx2dxI/mbdPvbexB2EJ https://groups.google.com/d/msg/mozilla.dev.platform/itl6mtx... (dbaron is Mozilla's representative to the W3C Advisory Committee as well being a principal engineer on the layout team and deeply involved in the development of CSS over the past decade.)
kstrauser 14y ago
From the first bug linked from the article (at https://bugzilla.mozilla.org/show_bug.cgi?id=762302 https://bugzilla.mozilla.org/show_bug.cgi?id=762302): The CSS Working Group has agreed to give the go-ahead to browser implementers to unprefix CSS3 Transitions, Transforms, and Animations: http://lists.w3.org/Archives/Public/www-style/2012Jun/0105.html So contrary to your comments, they're doing this because the W3 said that it's time to do so.
- gioele 14y ago
  > So contrary to your comments, they're doing this because the W3 said that it's time to do so. My point is that support for prefixed CSS properties should not be available in stable releases at all. What they should have done from the beginning (and from other comments seems it will be done in the future) is to enable experimental prefixed CSS properties only in dev builds (to demonstrate to the W3C working group the feasibility of those new properties) and remove such properties from stable releases. In this way the stable releases will have _only_ W3C approved prefixes, not the current mess of draft + CR + TR support.

by gioele 14y ago

mbrubeck 14y ago

That's exactly what Firefox developers like Henri Sivonen [1] and David Baron [2] think, and their proposals have a lot of support within Mozilla and a high chance of being adopted. It would be great to get other vendors on board too. [1] http://hsivonen.iki.fi/vendor-prefixes/ http://hsivonen.iki.fi/vendor-prefixes/ (see "Keep Experimental Features in Experimental Builds") [2] https://groups.google.com/d/msg/mozilla.dev.platform/itl6mtx2dxI/mbdPvbexB2EJ https://groups.google.com/d/msg/mozilla.dev.platform/itl6mtx... (dbaron is Mozilla's representative to the W3C Advisory Committee as well being a principal engineer on the layout team and deeply involved in the development of CSS over the past decade.)

kstrauser 14y ago

From the first bug linked from the article (at https://bugzilla.mozilla.org/show_bug.cgi?id=762302 https://bugzilla.mozilla.org/show_bug.cgi?id=762302): The CSS Working Group has agreed to give the go-ahead to browser implementers to unprefix CSS3 Transitions, Transforms, and Animations: http://lists.w3.org/Archives/Public/www-style/2012Jun/0105.html So contrary to your comments, they're doing this because the W3 said that it's time to do so.

gioele 14y ago
> So contrary to your comments, they're doing this because the W3 said that it's time to do so. My point is that support for prefixed CSS properties should not be available in stable releases at all. What they should have done from the beginning (and from other comments seems it will be done in the future) is to enable experimental prefixed CSS properties only in dev builds (to demonstrate to the W3C working group the feasibility of those new properties) and remove such properties from stable releases. In this way the stable releases will have _only_ W3C approved prefixes, not the current mess of draft + CR + TR support.