Chromium Blog: May 2013

Rich Notifications in Chrome

Thursday, May 23, 2013

App notifications send immediate alerts to users about important events as they happen. Chrome and Chrome OS already support basic web notifications, but rich notifications for Chrome packaged apps and extensions can enable users to act directly on these notifications and show rich content like lists and images. For those in beta channel, notifications now live in a center that is outside the browser, which allows them to receive notifications even when the browser is not open. Rich notifications are available in the latest beta channel builds on Windows, dev channel builds on ChromeOS, and will be coming to Mac OS X and Linux soon.
You can trigger a rich notification by calling the create method under the chrome.notifications module:

chrome.notifications.create(

‘id1’,{

type: ‘basic’,

iconUrl: ‘image1.png’,

title: ‘Althe Frazon’,

message: ‘Hi, what's going on tonight?’,

buttons: [{ title: ‘Call’,

iconUrl: ‘call.png’},

{ title: ‘Send Email’,

iconUrl: ‘email.png’}],

priority: 0},

function() { /* Error checking goes here */}

);

Apart from the basic notification type shown above, you can use other formats like image to show a preview of an image within the notification or list to coalesce multiple notifications from your app into a single one. For example, a mail app could show multiple unread emails within a single notification using the list type. You can also specify different priorities for notifications that determine how long they stay on the screen before moving into the notification center where they continue to live until dismissed by the app or user.

The notification center holds all current notifications and can be pulled up at any time from the launcher on ChromeOS or the system tray on Windows. Users can view and clear all of their notifications in the center, and also access settings to control which apps, extensions and websites can send them notifications.

Notification Center on Windows

Notification Center on ChromeOS

You can get started with rich notifications in your app or extension by trying out the Notify Test App and taking a look at the documentation on the Chrome developer site. We’d love your feedback so feel free to ask a question on Stack Overflow, start a discussion on our mailing list, or file a bug on our issue tracker. Posted by Justin DeWitt, Software Engineer and Notifications Knight

Chrome 28 Beta: A more immersive web, everywhere

Thursday, May 23, 2013

Beta channelFullscreen API on Chrome for AndroidFullscreen APIwebkitRequestFullScreen()requestFullscreen()zombie-inspired Chrome Experiment

Faster page loadsthreaded HTML parserExperimental new media features in Chrome for AndroidWeb AudioWebGLWebRTCabout:flagsmobile web demo in the Google I/O 2013 keynoteDeprecated featuresContent Security PolicynowdeprecatedContent-Security-PolicyX-WebKit-CSPmay not support itChrome ExtensionsdeprecatedRich Notifications Chrome APIcreateHTMLNotification()Other developer features in this release

You can now use CSS @supports conditional blocks to test whether Chromium supports certain property:value pairs.

The :unresolved CSS pseudoclass lets you style a Custom Element that hasn’t been registered in the browser yet. Custom Elements are part of Web Components.

As part of V8's continuing quest to make all JavaScript as fast as possible, recent optimizations have made the asm.js benchmarks more than twice as fast as prior versions of Chrome.

Chrome Apps and Extensions developers can now use rich notifications to proactively engage with users.

chromestatus.com+Google Chrome DevelopersBlink teamChrome team

Testing Chromium: SyzyASAN, a lightweight heap error detector

Monday, May 20, 2013

AddressSanitizerthousandsLLVMClangSyzyASANSyzygy

An instrumenter that injects instrumentation into binaries produced by the Microsoft Visual Studio toolchain.

A run-time library that replaces malloc, free, et al.

An RPC-based logging server that receives information about detected errors. This lets us get information safely out of sandboxed processes, like Chromium’s renderer.