Every time Firefox introduces a cool new feature, they emphasize how it's standard, or being put into the standardization process, and how every web developer will be able to use it.<p>Chrome? Not so much. And it isn't just that this news article left something out — the official Chrome blog[1] never hints that this feature will ever work on anything but Chrome.<p>To me it's uncomfortable how much Google's tactics with Chrome resemble Microsoft's "embrace and extend" from the late 90s. They seem to want everyone to make Chrome apps, not web apps. If that happens, ultimately we all suffer from the loss of an open web.<p>[1] <a href="http://chrome.blogspot.com/2013/05/richer-notifications-coming-to-chrome.html" rel="nofollow">http://chrome.blogspot.com/2013/05/richer-notifications-comi...</a>
One more thing that is coming (back) with Chrome 28 is packaged apps - stand-alone browser-based applications with access to file/network APIs (think Mozilla Prism/Fluid.app). I'm surprised they didn't mention it.
Legitimately excited to see Blink-based Chrome released. However, Chrome 28 <i>still</i> does not support un-prefixed CSS transitions, transforms, and animations. What gives?? <a href="http://www.chromium.org/blink#vendor-prefixes" rel="nofollow">http://www.chromium.org/blink#vendor-prefixes</a>
As the site has currently some problems, I can't read the article.<p>When is Chrome 28 arriving? I'm using Firefox and Chrome on my Mac. And today I've updated Flash for all browsers, except Chrome. The Flash plugin in Chrome is old now and needs an update. But no new Chrome there. :-(<p>Flash will bring Chrome down. They even have their own Flash bugs they don't fix as fast as Adobe(!).
Can't help but notice that the --disable-new-menu-style switch no longer works, which is terrible news if you hate Superfluous Google Whitespace as much as I do.