News for hackers. Stuff that matters.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by MatthewPhillips on Tuesday July 24, 2012 @09:23AM (#4285534)
> 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.

Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by jmillikin on Tuesday July 24, 2012 @11:14AM (#4286018)

  > 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, Transition... by kibwen on Tuesday July 24, 2012 @08:15AM (#4285318)
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 3D
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by derpmeister on Tuesday July 24, 2012 @09:06AM (#4285478)
Thanks! They should disable the flyout completion for now, though. It causes the input box to lose focus, can't type a command with that.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by gioele on Tuesday July 24, 2012 @08:17AM (#4285322)
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.

Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by tomjen3 on Tuesday July 24, 2012 @11:29AM (#4286077)
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, Transition... by lillycat on Tuesday July 24, 2012 @11:36AM (#4286107)
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, Transition... by Kilimanjaro on Tuesday July 24, 2012 @10:38AM (#4285846)
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?
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by lillycat on Tuesday July 24, 2012 @10:50AM (#4285901)
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.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by ck2 on Tuesday July 24, 2012 @08:01AM (#4285288)
Proving what time of day you submit on HN is critical

http://news.ycombinator.com/item?id=4278862

Still, good information to know.

Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by lillycat on Tuesday July 24, 2012 @09:20AM (#4285522)
And I did a search before to post!
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by ck2 on Tuesday July 24, 2012 @10:42AM (#4285859)
No worries.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by funksta on Tuesday July 24, 2012 @11:01AM (#4285952)
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)
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by Skalman on Tuesday July 24, 2012 @11:07AM (#4285984)
Yes, that works in my Firefox 16.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by funksta on Tuesday July 24, 2012 @11:22AM (#4286047)
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, Transition... by Killswitch on Tuesday July 24, 2012 @12:58PM (#4286572)
Bad timing on the naming... Aurora?
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by andrewstewart on Tuesday July 24, 2012 @01:17PM (#4286710)
Firefox Aurora has existed for the last few years. It's their preview release of stuff, equivalent to Chrome Canary.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by Killswitch on Tuesday July 24, 2012 @01:21PM (#4286737)
Yes, but in light of the current events, you'd think it'd be changed.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by specto on Tuesday July 24, 2012 @03:18PM (#4287423)
Why, this is a browser, not some evil plot? They could dedicate it if they wanted to.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by Killswitch on Tuesday July 24, 2012 @05:49PM (#4288191)
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.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by yen223 on Tuesday July 24, 2012 @11:29PM (#4289228)
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.

Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by hopefully on Tuesday July 24, 2012 @07:26AM (#4285195)
Ohhh, how long have I waited for this moment.
Re:Firefox 16 unprefix CSS Gradients, Animations, Transition... by PaulHoule on Tuesday July 24, 2012 @10:46AM (#4285880)
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, Transition... by sp332 on Tuesday July 24, 2012 @11:41AM (#4286135)
"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.