Chromium Blog

A New Approach to Printing

Thursday, April 15, 2010

demonstrated Google Chrome OS

codedocumentationherePosted by Mike Jazayeri, Group Product Manager

Technically speaking, what makes Google Chrome fast? (Part II)

Wednesday, April 14, 2010

published a series of video interviewsDNS pre-resolutionV8 JavaScript engineDOM bindingsWebKit

UI responsiveness

Posted by Min Li Chan, Product Marketing Manager

Calling all Students! Work on Chromium during Google Summer of Code

Tuesday, April 6, 2010

Google Summer of Codehandy ideas listmailing listirc channelgsoc websiteproposals are duePosted by Jeremy Moskovich, Software Engineer

Bringing improved support for Adobe Flash Player to Google Chrome

Tuesday, March 30, 2010

widely usednext generation browser plug-in APImaking available

When users download Chrome, they will also receive the latest version of Adobe Flash Player. There will be no need to install Flash Player separately.

Users will automatically receive updates related to Flash Player using Google Chrome’s auto-update mechanism. This eliminates the need to manually download separate updates and reduces the security risk of using outdated versions.

With Adobe's help, we plan to further protect users by extending Chrome's “sandbox” to web pages with Flash content.

postherePosted by Linus Upson, VP, Engineering

Google Chrome Developer Update - Geolocation and Incognito Extensions

Friday, March 26, 2010

What's New in Google Chrome?
The Google Chrome Dev channel has been updated to 5.0.356.2 for all platforms since our last developer post. It includes a few new goodies for developers:

Geolocation API: Run with the --enable-geolocation flag.
Incognito extensions
Unpacked extensions are now remembered across browser restarts.
Favicons for extension pages (define with a 16x16 image in your manifest.json).
setPopup() was added to browserAction and pageAction for dynamically changing which popup to show based on the selected tab.

Please keep in mind that these features are still under development and are not 100% stable yet. In addition to the above, there are a few new experimental features baking in /trunk. You can try them out with the --enable-experimental-extension-apis flag:

Samples and Tutorials
We’ve added a few new sample extensions tutorials to get you started:

Sample and tutorial to demonstrate using Google Analytics in your extensions
Extension to display, create, and update your Google Documents
Tutorial to demonstrate using OAuth in your extensions

Remember to follow us on Twitter: @ChromiumDev!
Posted by Eric Bidelman, Developer Advocate

Introducing the ANGLE Project

Thursday, March 18, 2010

We're happy to announce a new open source project called Almost Native Graphics Layer Engine, or ANGLE for short. The goal of ANGLE is to layer WebGL's subset of the OpenGL ES 2.0 API over DirectX 9.0c API calls. We're open-sourcing ANGLE under the BSD license as an early work-in-progress, but when complete, it will enable browsers like Google Chrome to run WebGL content on Windows computers without having to rely on OpenGL drivers.
Current browser implementations of WebGL need to be able to issue graphics commands to desktop OpenGL to render content. This requirement isn't a problem on computers running OS X or Linux, where OpenGL is the primary 3D API and therefore enjoys solid support. On Windows, however, most graphics-intensive apps use Microsoft Direct3D APIs instead of OpenGL, so OpenGL drivers are not always available. Unfortunately, this situation means that even if they have powerful graphics hardware, many Windows machines can't render WebGL content because they don't have the necessary OpenGL drivers installed. ANGLE will allow Windows users to run WebGL content without having to find and install new drivers for their system.
Because ANGLE aims to implement most of the OpenGL ES 2.0 API, the project may also be useful for developers who are working on applications for mobile and embedded devices. ANGLE should make it simpler to prototype these applications on Windows, and also gives developers new options for deploying production versions of their code to the desktop.
We hope that other WebGL implementors and others in the graphics community will join us to make ANGLE successful! For more info on ANGLE and to access the code repository, visit the new project on Google Code or join our discussion group.
Posted by Henry Bridge, Product Manager

Native Client and Web Portability

Wednesday, March 17, 2010

One of the most important principles of the web is portability: a web page renders and behaves the same way, regardless of the browser’s operating system or the type of hardware it’s running on. When we first released Native Client a year ago, we supported all popular operating systems (Windows, Mac OS X, and Linux) but only on machines with x86 processors. Today, we’re happy to say that you can build and run Native Client binaries for all of the most popular processor architectures: x86-32, x86-64, and ARM. Even better, our initial benchmarks indicate that Native Client executables perform at 97% of the speed of an unmodified executable on both ARM and x86-64 processors. These results indicate that a browser running on virtually any modern computer or cell phone could run a fast, performance-sensitive Native Client application.
However, we recognize that just running on today’s most popular architectures isn’t enough; if a new processor architecture emerges, it should be able to run all Native Client modules already released without requiring developers to recompile their code. That’s why we’re also developing technology that will enable developers to distribute a portable representation of Native Client programs using LLVM bitcode. Using this technology, a browser running on any type of processor could translate the portable representation into a native binary without access to the source code of the program.
If you’d like to review our instruction-set support or give us feedback about the technology, please visit our project on Google Code and join our Google Group. Posted by Brad Chen, Native Client Team