Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mass-unprefixing in Firefox 16

paulrouget.com

Post reply on HN
Print view View original

1–10 of 45 posts

Re: Mass-unprefixing in Firefox 16

#3

Post by bugschivers »

-moz-border-radius and -moz-box-shadow were both unprefixed in 13, I only know because I had a personal html page themed for firefox exclusively which was affected. There doesn't seem to be much comment on this unprefixing from Mozilla in any Official capacity, when my personal page was affected it was only by accident that I ran across this page https://developer.mozilla.org/en/Firefox_13_for_developers that mentions it. Just thought I'd mention this in case anyone was affected.

Re: Mass-unprefixing in Firefox 16

#6

Post by Achshar »

TazeTSchnitzel wrote: post #5

I personally think we should cut down on prefix use. Whilst it may be impractical to completely eliminate them, they are a PITA for developers, and have made the mobile web too heavily reliant on WebKit.

I know, i am using transitions/gradients on my project and i have to write 5(!) different rules just to set one property. This is for production code.

  background: -webkit-linear-gradient(#fff, #fdd 75%, #fcc);
  background: -moz-linear-gradient(#fff, #fdd 75%, #fcc);
  background: -ms-linear-gradient(#fff, #fdd 75%, #fcc);
  background: -o-linear-gradient(#fff, #fdd 75%, #fcc);
  background: linear-gradient(#fff, #fdd 75%, #fcc);
And this is used every time i have to set a gradient. I really wish there were some better options than prefixes. I am not surprised at all if developers move to supporting just webkit. This is a lot of work and maintaining. And without css variables, it is a mess to change a color. It is very tempting to just use the -webkit- version and probably a non prefixed one for future compatibility. 2 is far better than 5.

Edit: And i should mention, this is not a mobile website, it's a desktop site.

Re: Mass-unprefixing in Firefox 16

#7

Post by TazeTSchnitzel »

Achshar wrote: post #6
TazeTSchnitzel wrote: post #5

I personally think we should cut down on prefix use. Whilst it may be impractical to completely eliminate them, they are a PITA for developers, and have made the mobile web too heavily reliant on WebKit.

I know, i am using transitions/gradients on my project and i have to write 5(!) different rules just to set one property. This is for production code. background: -webkit-linear-gradient(#fff, #fdd 75%, #fcc); background: -moz-linear-gradient(#fff, #fdd 75%, #fcc); background: -ms-linear-gradient(#fff, #fdd 75%, #fcc); background: -o-linear-gradient(#fff, #fdd 75%, #fcc); background: linear-gradient(#fff, #fdd 75%, #…

Yeah. And that's without supporting older versions of syntax. You might need another 2 or 3 lines if you're unlucky, or possibly worse.

Many people including myself think prefixes should be eliminated entirely[1], or replaced with a single prefix for the experimental[2].

[1] http://paulirish.com/2012/vendor-prefixes-are-not-developer-...

[2] http://www.quirksmode.org/blog/archives/2010/03/css_vendor_p...

Re: Mass-unprefixing in Firefox 16

#8

Post by ars »

Achshar wrote: post #6
TazeTSchnitzel wrote: post #5

I personally think we should cut down on prefix use. Whilst it may be impractical to completely eliminate them, they are a PITA for developers, and have made the mobile web too heavily reliant on WebKit.

I know, i am using transitions/gradients on my project and i have to write 5(!) different rules just to set one property. This is for production code. background: -webkit-linear-gradient(#fff, #fdd 75%, #fcc); background: -moz-linear-gradient(#fff, #fdd 75%, #fcc); background: -ms-linear-gradient(#fff, #fdd 75%, #fcc); background: -o-linear-gradient(#fff, #fdd 75%, #fcc); background: linear-gradient(#fff, #fdd 75%, #…

Missed one:

    background: -webkit-gradient(linear, 0 0, 0 100%, from(#fff) color-stop(75%, #fdd) to(#fcc));
(I hope I got that syntax right.) This one should go above webkit-linear-gradient.

And it's also an example of why prefixes were invented - the syntax is totally different.

I think vendors should unprefix the moment their prefix matches the spec.

Re: Mass-unprefixing in Firefox 16

#9

Post by Natsu »

Achshar wrote: post #6
TazeTSchnitzel wrote: post #5

I personally think we should cut down on prefix use. Whilst it may be impractical to completely eliminate them, they are a PITA for developers, and have made the mobile web too heavily reliant on WebKit.

I know, i am using transitions/gradients on my project and i have to write 5(!) different rules just to set one property. This is for production code. background: -webkit-linear-gradient(#fff, #fdd 75%, #fcc); background: -moz-linear-gradient(#fff, #fdd 75%, #fcc); background: -ms-linear-gradient(#fff, #fdd 75%, #fcc); background: -o-linear-gradient(#fff, #fdd 75%, #fcc); background: linear-gradient(#fff, #fdd 75%, #…

Why not uses SASS and let mixins do that crap?

Re: Mass-unprefixing in Firefox 16

#10

Post by cleverjake »

ars wrote: post #8
Achshar wrote: post #6

Earlier quoted context omitted.

I know, i am using transitions/gradients on my project and i have to write 5(!) different rules just to set one property. This is for production code. background: -webkit-linear-gradient(#fff, #fdd 75%, #fcc); background: -moz-linear-gradient(#fff, #fdd 75%, #fcc); background: -ms-linear-gradient(#fff, #fdd 75%, #fcc); background: -o-linear-gradient(#fff, #fdd 75%, #fcc); background: linear-gradient(#fff, #fdd 75%, #…

Missed one: background: -webkit-gradient(linear, 0 0, 0 100%, from(#fff) color-stop(75%, #fdd) to(#fcc)); (I hope I got that syntax right.) This one should go above webkit-linear-gradient. And it's also an example of why prefixes were invented - the syntax is totally different. I think vendors should unprefix the moment their prefix matches the spec.

>>I think vendors should unprefix the moment their prefix matches the spec.

most of the time when all prefixed version are the same it means there isn't a CR for the spec, and it is therefore in flux. unprefixing it would mean sites would break if and when it is changed before reaching recommendation.

Post reply on HN