Chromium Blog
News and developments from the open source browser project
Chrome app launcher developer preview
Wednesday, February 20, 2013
Today, on the
Chrome dev channel for Windows
, you can try the Chrome app launcher--a dedicated home for your apps which makes them easy to open outside the browser. This is the same experience as the app launcher on Chromebooks, but for other platforms. It’s available on Windows now, and will be coming to Mac OS X and Linux soon.
You’ll need to install a
Chrome packaged app
, such as IRC client
CIRC
or
Text Drive
, in order to try out the Chrome app launcher. Chrome packaged apps deliver a native-like experience across multiple platforms with the security properties of a web page. Just like web apps, packaged apps are written in HTML, JavaScript, and CSS. But packaged apps launch outside the browser, work offline by default, and have access to
powerful APIs
not available to web apps.
You’ll get the app launcher as an icon on your Windows taskbar the first time you install a packaged app. Chrome packaged apps are not yet searchable on the Chrome Web Store - but you can
build
your own packaged app,
upload
it to the Chrome Web Store and access it via its direct link.
Try out the app launcher and let us know what you think. If you have any questions or comments, you can use
Stack Overflow
or
chromium-apps
. File your bugs and feature requests
here
.
Posted by Sriram Saroop, Product Manager
Using WebP to Improve Speed
Thursday, February 7, 2013
Since speed is critical for a good experience when using the web, at Google we’re always exploring ways to make the web faster. As it turns out, one of the biggest bang-for-the-buck ways to do that is by replacing JPEG and PNG images with
WebP
. WebP offers significantly better compression than these legacy formats (around
35% better
in most cases), and when you consider that
over 60%
of typical page sizes are images, the benefits can be substantial. WebP translates directly into less bandwidth consumption, decreased latency, faster page loads, better battery consumption on mobile, and overall happier users.
Case in point: the
Chrome Web Store
uses many large promotional images and tiles on its home page, making it a very heavyweight page. The team was eager to find ways to improve its speed, without sacrificing the user experience or giving up image quality. WebP to the rescue!
By converting PNGs and JPEGs to WebP, the Chrome Web Store was able to reduce image sizes by about 30% on average (here’s one sample image in
WebP
at 8.3kB and
JPEG
at 32kB). Given the number of requests Chrome Web Store serves, this adds up to
several terabytes
of savings every day.
For users, the rubber meets the road when it comes to how fast the page loads though. On this score, with WebP we were able to reduce average home page load time by nearly one-third — a huge benefit for our users.
To implement WebP, the team first added transcoding support to the image request pipeline; then at runtime the site checks whether the client browser supports WebP and requests the WebP version for each image when it does. The effort to implement it turned out to be not much work for a lot of benefit.
To find out more about how you can make your site faster, visit our
Make the Web Faster
site and dive into
WebP
.
Posted by Stephen Konig, Product Manager
Updates to manifest V1 Chrome Web Store items to be blocked in March
Wednesday, February 6, 2013
Last year, Chrome introduced
manifest V2
to Apps and Extension developers, which brings a variety of security and API improvements such as a default
Content Security Policy
. As of Chrome 18, manifest V1 was officially deprecated. At the time, we published our
manifest version support schedule
to give developers transparency and insight into our plans for migrating to the new version.
Today, we’re announcing a slight update to that schedule, to let developers know that they have until Monday, March 4, 2013 to make updates to their existing manifest V1-based items. After that date, the
Chrome Web Store
will
block all updates
to products based on manifest V1 unless the update includes switching it to manifest V2.
Developers are strongly encouraged to migrate their items to manifest V2 now. Follow the
migration tutorial
, and you can always contact us on the
chromium-apps forum
and
our G+ page
with any questions you may have.
Posted by Joe Marini, Developer Advocate
Introducing “Find Your Way to Oz”, a new Chrome Experiment
Tuesday, February 5, 2013
Earlier today we unveiled
Find Your Way To Oz,
a new Chrome Experiment inspired by the upcoming feature film
Oz The Great and Powerful
. Developed by
UNIT9
, this experiment brings together Disney’s unique storytelling tradition and the power of the web platform, allowing users to interact with the web in a completely new way.
The desktop version of “Find Your Way To Oz” uses many of the open web’s more advanced features:
Immersive Graphics: The experiment uses
WebGL
for the main 3D environment,
CSS3
features such as CSS Transitions for various visual embellishments, and GLSL shaders for the tornado’s ominous look and feel.
Rich Audio: As the user explores the experiment, the 3D sound dynamically adapts thanks to the
Web Audio API
. The same API powers the experiment’s music composing section.
Camera-based interactions: Through WebRTC’s
getUserMedia
API
, users can become circus characters or record their own mini-movies.
The experiment’s mobile web version also uses cutting-edge web technologies. These include graphics features such as accelerated
3D transforms
and
sprite sheets
as well as mobile hardware features like camera, multi-touch, gyroscope and accelerometer. Together they create an experience that can normally only be found in native apps.
To learn more about how this experiment was built, read our
technical case study
and join us for a Google Developers Live event on February 11th at 11 a.m. GMT where we’ll be talking to the team behind the project. Alternatively, use Chrome’s
developer tools
to see how the experiment works on your own, perhaps finding in the process your own path to the yellow brick road.
Posted by Max Heinritz, Product Magician (Manager)
Hello Firefox, this is Chrome calling!
Monday, February 4, 2013
For the first time, Chrome and Firefox can “talk” to each other via
WebRTC
. WebRTC is a new set of technologies that brings clear crisp voice, sharp high-definition (HD) video and low-delay communication to the web browser.
From the very beginning, this joint WebRTC effort was embraced by the open web community, including engineers from the Chrome and Firefox teams. The common goal was to help developers offer rich, secure communications, integrated directly into their web applications.
In order to succeed, a web-based communications platform needs to work across browsers. Thanks to the work and participation of the
W3C
and
IETF
communities in developing the platform, Chrome and Firefox can now communicate by using standard technologies such as the
Opus
and
VP8
codecs for audio and video,
DTLS
-
SRTP
for encryption, and
ICE
for networking.
To try this yourself, you’ll need desktop
Chrome 25 Beta
and
Firefox Nightly for Desktop
. In Firefox, you'll need to go to
about:config
and set the
media.peerconnection.enabled
pref to "
true
”. Then head over to the
WebRTC demo site
and start calling.
For developers looking to include this functionality in their own apps, there are a few places you can go to get more information. You can look at the
source code
of the AppRTC demo, a
library
that makes writing cross-browser WebRTC apps a snap, and a
document
detailing some of the minor differences between browsers.
You can read more from Mozilla’s hacks blog
here
and view our first “Official” call at the video below:
Posted by Maire Reavy, Firefox Media Product Lead and Serge Lachapelle, Chrome Product Manager
Show off Your Security Skills: Pwn2Own and Pwnium 3
Monday, January 28, 2013
Security is one of the core tenets of Chrome, but no software is perfect, and security bugs slip through even the best development and review processes. That’s why we’ve continued to engage with the security research community to help us find and fix vulnerabilities. Recently, HP’s
Zero Day Initiative
(ZDI) announced details for the annual
Pwn2Own competition
, to be held at the
CanSecWest
security conference taking place March 6-8 in Vancouver, BC. This year we’ve teamed up with ZDI by working together on the Pwn2Own rules and by underwriting a portion of the winnings for all targets. The new rules are designed to enable a contest that significantly improves Internet security for everyone. At the same time, the best researchers in the industry get to showcase their skills and take home some generous rewards.
Today we’re announcing our third Pwnium competition—Pwnium 3. Google Chrome is already featured in the Pwn2Own competition this year, so Pwnium 3 will have a new focus: Chrome OS.
We’ll issue Pwnium 3 rewards for Chrome OS at the following levels, up to a total of $3.14159 million USD:
$110,000: browser or system level compromise in guest mode or as a logged-in user, delivered via a web page.
$150,000: compromise with device persistence -- guest to guest with interim reboot, delivered via a web page.
We believe these larger rewards reflect the additional challenge involved with tackling the security defenses of Chrome OS, compared to traditional operating systems.
The attack must be demonstrated against a base (WiFi) model of the Samsung Series 5 550 Chromebook, running the latest stable version of Chrome OS. Any installed software (including the kernel and drivers, etc.) may be used to attempt the attack. For those without access to a physical device, note that the
Chromium OS developer’s guide
offers assistance on getting up and running inside a virtual machine.
Standard Pwnium rules apply: the deliverable is the full exploit plus accompanying explanation and breakdown of individual bugs used. Exploits should be served from a password-authenticated and HTTPS-supported Google property, such as Google App Engine. The bugs used must not be known to us or fixed on trunk. We reserve the right to issue partial rewards for partial, incomplete or unreliable exploits.
Pwnium 3 will take place on-site at the CanSecWest conference on March 7.
Posted by Chris Evans, Google Chrome Security Team
Native Client support on ARM
Tuesday, January 22, 2013
Native Client
(NaCl) enables Chrome to run high-performance apps compiled from your C and C++ code. One of the main
goals
of Native Client is to be architecture-independent, so that all machines can run NaCl content. Today we’re taking another step toward that goal: our
Native Client SDK
now supports ARM devices, from
version 25
and onwards.
If your app uses Native Client and newlib, you’ll now be able to reach users on ARM devices by simply adding an ARM
.nexe
to your app and making a small adjustment to the Native Client
manifest
. Just get the newest SDK, and you’ll have all the tools you need.
While this will help provide more apps to users with ARM devices, we’re far from done. In 2013 the next generation of Native Client, called
Portable Native Client
, will introduce true architecture-independence by using
LLVM
bitcode as the wire format. With Portable Native Client, we’ll be able to support not just today’s architectures, but also those of tomorrow – and developers won’t have to recompile their app.
We look forward to your technical questions on
Stack Overflow
as well as comments in the discussion
forum
.
Posted by David Sehr, Software Engineer
Labels
$200K
1
10th birthday
4
abusive ads
1
abusive notifications
2
accessibility
3
ad blockers
1
ad blocking
2
advanced capabilities
1
android
2
anti abuse
1
anti-deception
1
background periodic sync
1
badging
1
benchmarks
1
beta
83
better ads standards
1
billing
1
birthday
4
blink
2
browser
2
browser interoperability
1
bundles
1
capabilities
6
capable web
1
cds
1
cds18
2
cds2018
1
chrome
35
chrome 81
1
chrome 83
2
chrome 84
2
chrome ads
1
chrome apps
5
Chrome dev
1
chrome dev summit
1
chrome dev summit 2018
1
chrome dev summit 2019
1
chrome developer
1
Chrome Developer Center
1
chrome developer summit
1
chrome devtools
1
Chrome extension
1
chrome extensions
3
Chrome Frame
1
Chrome lite
1
Chrome on Android
2
chrome on ios
1
Chrome on Mac
1
Chrome OS
1
chrome privacy
4
chrome releases
1
chrome security
10
chrome web store
32
chromedevtools
1
chromeframe
3
chromeos
4
chromeos.dev
1
chromium
9
cloud print
1
coalition
1
coalition for better ads
1
contact picker
1
content indexing
1
cookies
1
core web vitals
2
csrf
1
css
1
cumulative layout shift
1
custom tabs
1
dart
8
dashboard
1
Data Saver
3
Data saver desktop extension
1
day 2
1
deceptive installation
1
declarative net request api
1
design
2
developer dashboard
1
Developer Program Policy
2
developer website
1
devtools
13
digital event
1
discoverability
1
DNS-over-HTTPS
4
DoH
4
emoji
1
emscriptem
1
enterprise
1
extensions
27
Fast badging
1
faster web
1
features
1
feedback
2
field data
1
first input delay
1
Follow
1
fonts
1
form controls
1
frameworks
1
fugu
2
fund
1
funding
1
gdd
1
google earth
1
google event
1
google io 2019
1
google web developer
1
googlechrome
12
harmful ads
1
html5
11
HTTP/3
1
HTTPS
4
iframes
1
images
1
incognito
1
insecure forms
1
intent to explain
1
ios
1
ios Chrome
1
issue tracker
3
jank
1
javascript
5
lab data
1
labelling
1
largest contentful paint
1
launch
1
lazy-loading
1
lighthouse
2
linux
2
Lite Mode
2
Lite pages
1
loading interventions
1
loading optimizations
1
lock icon
1
long-tail
1
mac
1
manifest v3
2
metrics
2
microsoft edge
1
mixed forms
1
mobile
2
na
1
native client
8
native file system
1
New Features
5
notifications
1
octane
1
open web
4
origin trials
2
pagespeed insights
1
pagespeedinsights
1
passwords
1
payment handler
1
payment request
1
payments
2
performance
20
performance tools
1
permission UI
1
permissions
1
play store
1
portals
3
prefetching
1
privacy
2
privacy sandbox
4
private prefetch proxy
1
profile guided optimization
1
progressive web apps
2
Project Strobe
1
protection
1
pwa
1
QUIC
1
quieter permissions
1
releases
3
removals
1
rlz
1
root program
1
safe browsing
2
Secure DNS
2
security
36
site isolation
1
slow loading
1
sms receiver
1
spam policy
1
spdy
2
spectre
1
speed
4
ssl
2
store listing
1
strobe
2
subscription pages
1
suspicious site reporter extension
1
TCP
1
the fast and the curious
23
TLS
1
tools
1
tracing
1
transparency
1
trusted web activities
1
twa
2
user agent string
1
user data policy
1
v8
6
video
2
wasm
1
web
1
web apps
1
web assembly
2
web developers
1
web intents
1
web packaging
1
web payments
1
web platform
1
web request api
1
web vitals
1
web.dev
1
web.dev live
1
webapi
1
webassembly
1
webaudio
3
webgl
7
webkit
5
WebM
1
webmaster
1
webp
5
webrtc
6
websockets
5
webtiming
1
writable-files
1
yerba beuna center for the arts
1
Archive
2024
Jun
May
Apr
Mar
Feb
2023
Nov
Oct
Sep
Aug
Jun
May
Apr
Feb
2022
Dec
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2021
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2020
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2019
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2018
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Follow @ChromiumDev
Give us feedback in our
Product Forums
.