Between hurricanes and hericanes, you could easily have missed the technology news. Released yesterday in public beta, Google Chrome is a standards-compliant web browser created to erode Microsoft’s browser dominance (i.e. to boost Google’s web dominance) while also rethinking what a browser is and does in the age of web apps and Google’s YouTube.

The new browser is based on Webkit, the advanced-standards-compliant, open source browser engine that powers Apple’s Safari for Mac and PC, but Chrome currently runs only in Windows. You figure that out.

Here are the new browser’s terms of service.

And here’s an important early bug report from Jeremy Jarratt: Google Chrome wrongly displays alternate styles as if active, thus “breaking” websites that use them. (Here’s more about alternate style sheets, from Paul Sowden’s groundbreaking 2001 A List Apart article.)

To compete with Microsoft, the new browser must offer what other browsers do not. The risk inherent in that proposition is a return to proprietary browser code. It is not yet clear to me whether Chrome will compete the wrong way—offering Chrome-only features based on Chrome-only code, thus prompting Microsoft to rethink its commitment to standards—or the right way.

Competing by offering features other browsers do not (easier downloads, streamlined user interface) or by consolidating other browsers’ best features (Opera’s Speed Dial, Firefox’s auto-complete) avoids this risk, as improvements—or at any rate, changes—to the browser’s user interface have no bearing on the display of existing web content.

Competing by supporting web standards ahead of the pack, although not entirely without risk, would also be a reasonable and exciting way to compete. When one browser supports a standard, it goads other browser makers into also supporting it. Because Safari, for instance, supports @font-face, Firefox is not far behind in supporting that CSS spec. @font-face raises font licensing problems, but we’ll discuss those another time. The risk that concerns us here is when a browser supports an emerging specification before it is finalized, thus, essentially, freezing the spec before it is ready. But that is the traditional dance between spec authors and browser makers.

For web standards and web content, we once again live in interesting times. Welcome, Chrome!

Tags: google, chrome, googlechrome, beta, software, browsers, standards, webbrowsers, webstandards, bugs, standards-compliant, alternatestyles, alternatecss

Filed under: A List Apart, Ajax, Applications, Browsers, Design, Google, Microsoft, bugs, chrome

Q. i have been using your son of moto [blogger template] to build my blogspots. why do i have to have two empty, wide, side fields? pls take a look at the above reference blog. i have to put all the content in the middle, rather narrow field.

A. We regret that we cannot provide technical support for templates we designed in 2004. Please check Blogger’s Help pages and see if they answer your concerns.

Bastardized, corrupted versions of these templates—versions we did not design, based on our work but not done by us—show up all over the web. We don’t know if these bastardized, corrupted versions are authorized (i.e. we don’t know if the republishers paid a licensing fee to Google, who commissioned the templates in the first place). Millions of people use these templates, or unauthorized hacks of these templates. If you need help changing the templates to suit your needs, kindly contact your service provider.

The original templates are part of the 2004 standards-based redesign of Blogger on which we and others toiled. Google paid the least money any of us had ever received on a web design job. But we would have done the work for free. It was all about creating web-standards-based templates—about getting standards out there in a big way: a way only a product with as many users as Blogger, and an owner as powerfully influential as Google, could assure. Finances were beside the point. The reward was making standards-based stuff for millions of people to use and enjoy.

Four years on, we still get a warm feeling out of having worked on the project. But that’s not all we get. Several times a week, we get e-mails from people who want to alter our templates but lack technical know-how. We regret that we cannot debug the style sheets of the universe.

Tags: moto, son of moto, blogger, templates

Filed under: Blogs and Blogging, Google, blogger