On: Chrome 28 arrives with Blink, rich notifications f...

[ahoge]

> Every time Firefox introduces a cool new feature, they emphasize how it's standard, or being put into the standardization process [...]

No, not really. They just added `let`, iterators/generators, destructuring assignment, etc in 2006 without asking anyone. Today, you can even use it without opting-in (via: type="application/javascript;version=1.7"). This stuff is supposed to be in ES6 in the future.

Same deal with APNG. They just added it in 2008. It also isn't standardized.

Firefox also supports "jar:" URLs for some reason. Here is a demo: http://kaioa.com/b/0907/jartest.html

Well, all browser vendors are like that and it's generally a good thing. If one of those experimental things turns out to be useful, other browsers will adopt it. Good examples for that are things like JavaScript, XHR, or text-overflow:ellipsis.

[nnethercote → ahoge]

2006 was seven years ago; circumstances were different.

Nowadays, at least for the JS stuff, we're much more circumspect about adding features, and really only do it for ES.next kind of stuff.

[icebraining → ahoge]

No, not really. They just added `let`, iterators/generators, destructuring assignment, etc in 2006 without asking anyone. Today, you can even use it without opting-in (via: type="application/javascript;version=1.7"). This stuff is supposed to be in ES6 in the future.

Parent said or being put into the standardization process. All those ES6 features are obviously in the standardization process.

[ahoge → icebraining]

> All those ES6 features are obviously in the standardization process.

Today they are, yes. Just like text-overflow:ellipsis (which was introduced with IE6) is now part of CSS3.

[diroussel → ahoge]

And indeed most of the best web features were added before standardization.

And some others that were standards first, like xhtml, well, didn't go so well.