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

Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

hacks.mozilla.org

Post reply on HN
Print view View original

11–20 of 25 posts

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#11

Post by PaulHoule »

ugh...

i'd like to see firefox slow down with the features and focus on stability.

firefox seems to be in the same boat as microsoft office, eclipse, gnome, and almost all GUI software. each new version adds meaningless features while bugs proliferate unchecked. (Given that this problem affects GUI apps of all kinds, perhaps it can't be solved?)

the latest thing that drives me up the wall about Firefox is that it's continually alerting me that my "plug ins are out of date" but as of the last few months the "plug in update" procedures are all broken -- I'm scared to update Java because the last time I did that I broke all my Java apps, and it seems like updates to Adobe products on windows don't work at all today.

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#12

Post by lillycat »

Kilimanjaro wrote: post #9

My blood boils every time I see an odd change in a perfectly fine way of doing things. Compare this: linear-gradient(top,#fff,#000) to this linear-gradient(to bottom,#fff,#000) Why?

The CSS WG wanted that both the and the keywords to be consistent: both are indicating a direction now. The 'to' was added in order to let the old and new syntax coexist during the transition time.

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#15

Post by jmillikin »

MatthewPhillips wrote: post #8

> IndexedDB has reached Candidate Recommendation status and has been unprefixed too. This is amazing. Folks, this is far more important than CSS. Firefox has the most complete implementation of IndexedDB. More than anything else, it is what will enable us to write completely client-side applications.

  > More than anything else, it is what will enable us to
  > write completely client-side applications.
It seems to me that developers have been writing completely client-side applications for forty years.

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#16

Post by funksta »

Skalman wrote: post #14
funksta wrote: post #13

I can't tell from the post, but is the argument for linear gradients still optional? Ie. is the following still valid? linear-gradient(#fff, #eee)

Yes, that works in my Firefox 16.

Great, thanks! I find I use top-to-bottom gradients about 90% of the time, so I'm glad the succinct form is still valid.

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#17

Post by tomjen3 »

gioele wrote: post #5

For all the lovers of the "prefixes are not useful, just do without them": > Also the changed: before, 0deg pointed to the right; now it points, consistently with other angles in the CSS spec, to the top.

Which is consistent with how all the other browser does it.

And I don't doubt that the prefix debacle is the reason they are getting rid of them now.

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#18

Post by lillycat »

tomjen3 wrote: post #17
gioele wrote: post #5

For all the lovers of the "prefixes are not useful, just do without them": > Also the changed: before, 0deg pointed to the right; now it points, consistently with other angles in the CSS spec, to the top.

Which is consistent with how all the other browser does it. And I don't doubt that the prefix debacle is the reason they are getting rid of them now.

No, Opera and Microsoft are implementing the new syntax too (IE 10 unprefixed and Presto 2.12, which is under development, too).

Hopefully WebKit will follow soon (if somebody has the bug#, I'm interested)

Re: Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms

#19

Post by sp332 »

PaulHoule wrote: post #11

ugh... i'd like to see firefox slow down with the features and focus on stability. firefox seems to be in the same boat as microsoft office, eclipse, gnome, and almost all GUI software. each new version adds meaningless features while bugs proliferate unchecked. (Given that this problem affects GUI apps of all kinds, perhaps it can't be solved?) the latest thing that drives me up the wall about Firefox is that it's c…

"Each version adds meaningless features" This is because the new rapid-release system lets them publish each feature as soon as it is ready. Since big features generally take longer, it's not surprising that each little release has fewer big features.
Post reply on HN