Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms(hacks.mozilla.org)
hacks.mozilla.org
Firefox 16 unprefix CSS Gradients, Animations, Transitions & Transforms
http://hacks.mozilla.org/2012/07/aurora-16-is-out
9 comments
> More than anything else, it is what will enable us to
> write completely client-side applications.
The new developer command-line interface (Shift+F2) looks really neat, though I'll have to play with it to see if it really turns out to be useful. Here's a list of commands:
addon - Manipulate add-ons
break - Manage breakpoints
calllog - Commands to manipulate function call logging
console - Commands to control the console
cookie - Display and alter cookies
dbg - Manage debugger
edit - Tweak a page resource
export - Export resources
firebug - Web Development Evolved
help - Get help on the available commands
inspect - Inspect a node
pagemod - Make page changes
pref - Commands to control settings
resize - Control Responsive Design Mode
restart - Restart Firefox
screenshot - Save an image of the page
tilt - Visualize the webpage in 3DThanks! They should disable the flyout completion for now, though. It causes the input box to lose focus, can't type a command with that.
For all the lovers of the "prefixes are not useful, just do without them":
> Also the <angle> changed: before, 0deg pointed to the right; now it points, consistently with other angles in the CSS spec, to the top.
> Also the <angle> 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.
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)
Hopefully WebKit will follow soon (if somebody has the bug#, I'm interested)
My blood boils every time I see an odd change in a perfectly fine way of doing things.
Compare this:
Compare this:
linear-gradient(top,#fff,#000)
linear-gradient(to bottom,#fff,#000)
The CSS WG wanted that both the <angle> 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.
Proving what time of day you submit on HN is critical
http://news.ycombinator.com/item?id=4278862
Still, good information to know.
http://news.ycombinator.com/item?id=4278862
Still, good information to know.
I can't tell from the post, but is the <angle> argument for linear gradients still optional? Ie. is the following still valid?
linear-gradient(#fff, #eee)Bad timing on the naming... Aurora?
Firefox Aurora has existed for the last few years. It's their preview release of stuff, equivalent to Chrome Canary.
Yes, but in light of the current events, you'd think it'd be changed.
Why, this is a browser, not some evil plot? They could dedicate it if they wanted to.
No, but at the same time, it's just respectful to not keep the codename of a project that is related to such a tragic event.
My heart goes out to the victims and their families of the Aurora incident.
However, "Aurora" as a name is simply too common to be replaced.
However, "Aurora" as a name is simply too common to be replaced.
Ohhh, how long have I waited for this moment.
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.
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.
"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.
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.