The Download Blog

Google has issued the first developer preview version of its Chrome browser to reach the version 4.x milestone, a phase that should bring some advanced features in the forthcoming HTML 5 specification for Web pages but that for now just sports a cloud-based bookmark synchronization tool.

Google's Chrome browser is getting a bookmark sync tool.

(Credit: Screenshot by Stephen Shankland/CNET)

"Once you set up sync from the Tools menu, Chrome will then upload and store your bookmarks in your Google Account. Anytime you add or change a bookmark, your changes will be sent to the cloud and immediately broadcast to all other computers for which you've activated bookmark sync," programmer Tim Steele said in a blog post Monday. Steele introduced the Chrome bookmark feature less than three weeks ago.

I set up the bookmarks feature with no trouble on version 4.0.201.1 of Chrome for Windows; note that to get it to work, you must specifically enable it at launch by adding the "--enable-sync" option to the launch command. The wrench menu (think tools) offers the new menu item to synchronize bookmarks. Clicking on it springs open a dialog box that prompts you to log in with a Google account; doing so then sends the bookmarks to the server.

The Mac version of Chrome--which by the way now enables by default plug-ins such as Adobe Systems' Flash and has grown much more stable--didn't yet support bookmark sync Monday night, so I couldn't test the actual synchronization itself on my present home setup.

Google doesn't draw much attention to version numbers, using them more as developer placeholders than beacons for marketing or support purposes. Google updates Chrome automatically, so users often get new versions without even knowing about it. But the new versions can indicate when the company is making significant changes behind the scenes.

After leaving much of the creation of a new version of HTML to Apple, Google, Opera, and Mozilla, Microsoft has begun sinking its teeth into the Web standard.

The move adds clout to the effort to renovate HyperText Markup Language, the standard used to describe Web pages, which last was formally updated in 1999. In a mailing list posting on Friday, the software giant offered a host of questions and concerns with the present proposal.

"As part of our planning for future work, the IE team is reviewing the current editor's draft of the HTML5 spec and gathering our thoughts. We want to share our feedback and discuss this in the working group," said Internet Explorer Program Manager Adrian Bateman in the message. "I will post our notes as we collect them so we can iterate on our thinking more quickly. At this stage we have more questions than answers, but I believe that discussing them in public is the best way to make progress."

HTML 5 in its current draft form includes a number of significant advancements, notably several that make the Web a better foundation for applications, not just static Web pages. Among the present HTML 5 features are built-in video and audio, the ability to store data on a local computer to enable use of Web applications even when offline, Web Workers that can perform computational chores in the background without bogging down Web application responsiveness, Canvas for creating sophisticated two-dimensional graphics, and drag-and-drop for better Web application user interfaces.

Features that Google brought to its developer preview version of Chrome--themes, a revamped new-tab page, a tweaked Omnibox for searching and entering Web addresses, and support for HTML 5 video--have now arrived on the browser's better tested beta version intended for broader use.

Individually, these features in Chrome 3.0.195.4 (download) are niceties. Collectively, they show Google is steadily moving ahead with its browser project, which was ambitious even before Chrome OS arrived on the scene. Fighting for a piece of the browser market is tough, but offering an operating system solely for Web-based applications is a lot tougher.

Chrome themes, such as this one called Grass, are in the new Chrome beta.

(Credit: Screenshot by Stephen Shankland/CNET)

After some on-again, off-again wavering, I've gone back to Chrome as my default browser. I like its interface and a handful of features, but the main advantage is its priority on speed. Google's Chrome ambition is to improve the Web as a foundation for applications and more generally to get people to do more online, and speed is of the essence.

That's why the shiny new features such as Chrome themes actually are less interesting to me than some of the fine print in Google's announcement of the new beta:

Beyond the improvements in JavaScript execution in this latest beta, there are a host of other improvements that should help Google Chrome make the most of your network connection. For example, when you open a new Web page while other Web pages are still loading, Google Chrome is now smarter about prioritizing the requests for the new page--for instance, fetching text, images, and video for your new page--ahead of the requests from the older pages. Loading pages on this beta release should also be faster than ever with DNS caching, more efficient DOM bindings, and using V8 for proxy auto-config.

OK, so that gets deep in the weeds at the end there, but suffice it to say that Google is tackling browser speed in a number of areas, not just its V8 engine for executing Web programs written in JavaScript.

Google gets dinged with some justification for moving sluggishly with Chrome. The Mac OS X and Linux versions are only now beginning to come into their own, for example. But there's a subtext to that criticism that bears mentioning.

Specifically, it looks to me as if some perceptions are shifting from "Why should I bother with Chrome?" to "Google isn't moving fast enough with Chrome." That shows expectations are shifting in Google's favor. It positions the company better to win over converts through the gradual delivery of extensions and other high-demand features.

Of course, a lot of my feedback is from change-embracing early adopters who care, sometimes passionately, about browsers. Getting Chrome to appeal to mainstream folks will be another, harder challenge for Google.

XHTML 2, we hardly knew you.

XHTML 2, a technology intended to build a more powerful Web from the ground up, met a quiet end last week, spotlighting the difficulties of standardization in a fast-moving Internet. Introduced in 2002, XHTML 2 was a centerpiece of standards work at the World Wide Web Consortium (W3C).

But incompatibility with the existing Web and a direction at odds with Web developers' desires doomed it to a slow demise. On Thursday, after a long reconciliation with browser makers who'd struck off in a different direction, the W3C announced that it will wind down development of XHTML 2 this year.

Ultimately, Web browser makers had the upper hand in charting the Web's future.

(Credit: Stephen Shankland/CNET)

Instead, the group will channel those resources into standardizing what the browser makers have been toiling on all these years: HTML 5, a sprawling collection of new features to improve the present Hypertext Markup Language. Although elements of XHTML 2 will live on in HTML 5, overall, the browser makers prevailed.

"XHTML 2 was a beautiful specification of philosophical purity that had absolutely no resemblance to the real world," said Bruce Lawson, HTML 5 evangelist for browser maker Opera.

So what went wrong? In short, the Web has many masters, but the ones with final say over its nature are those who build it page by page, not the standards group trying to create a new foundation.

XHTML 2 was designed to reform the Web as a medium for publishing documents, but the developers--and the browser makers who listened closely to those developers--instead wanted a platform for interactive applications. And while that direction prevailed, its incarnation in HTML 5 faces its own set of challenges now.

The consensus for HTML 5 support has been building for years, and the W3C already had been increasing its involvement in its standardization well before it decided to put an end to much of the competing XHTML 2 standard. Although the HTML-XHTML split has been fractious at times, there's inescapable tension between standards groups trying to chart the future and vendors whose products relate to those standards.

"I will not say it's been the smoothest way of doing things, but it's not an unnatural way for things to proceed," said Mike Smith, leader of HTML work at W3C, speaking of the reconciliation process that rejuvenated the W3C's HTML work. "Vendors are the ones who drive innovation on the Web for the most part."

Why XHTML?
So if it's so clear today that HTML 5 is the way to go, why was so much energy, time, and research invested in XHTML 2? It was an attempt start afresh without HTML's shortcomings.

The X in XHTML stands for XML, which in turn stands for Extensible Markup Language. XML is a broad technology that uses a strict set of tags to label different types of content in a document, and XHTML was engineered specifically for the Web. XHTML brought rigor to the loosey-goosey and slap-dash world of HTML, and it would have permitted developers to employ a broader range of computing engines called parsers to digest and process the XML, Smith said.

XHTML "was a cleaner and better-architected version of HTML," Smith said. And in its earlier years, it had support. "At the time when XHTML 2 was first conceived and specified in the early drafts, most everybody thought it was a good idea. A lot of people in hindsight want to look back at it now and make the claim that they knew it wasn't going to have success," Smith said.

XHTML 2.0 made it to working draft stage, but only parts of the specification will live on in HTML 5.

One example of its utility is the tight coupling of textual information with a graphs encoded with the SVG, or Scalable Vector Graphics format, Smith said. Another advantage was better browsing with the limited abilities of mobile phones.

One of the big problems with XHTML 2 was that it wasn't backwards compatible, though. Not only could it not be used to display existing Web pages, but Web browsers had to be expanded with an entirely new engine for handling the XML. Notably, Microsoft's Internet Explorer, the dominant browser by far, couldn't handle XHTML on its own.

Another problem was that there was plenty of demand for improvements to HTML, which W3C had declared finished with version 4.01 in 1999.

"People were so focused on XHTML 2 that they were substantially less interested in modifying the application model and introducing new features to HTML that developers were clamoring for," said Arun Ranganathan, standards evangelist for Mozilla, the organization behind the Firefox browser. "We felt the standards going on at the time...were disconnected from a large majority of developers.

Microsoft agrees with its browser rival.

"We've never heard a strong request from our developer audience and customers for XHTML 2," said Amy Barzdukas, general manager for IE.

Enter WHATWG
One crucial moment came five years ago when Opera and Mozilla representatives showed the W3C an idea called WebForms for improving HTML. "We jointly presented this paper to W3C, who rejected it," Lawson said.

Mozilla's Brendan Eich and Opera's Ian Hickson were displeased with how things went. "The best way to help the Web is to incrementally improve the existing web standards," concluded Eich, founder of the JavaScript Web programming language, after the meeting in a blog post.

Eich also announced there an Opera and Mozilla plan to take that evolutionary route. They launched an open e-mail list called WHATWG, short for Web Hypertext Application Technology Working Group. Apple, which offers its own Safari browser, soon began participating, too.

"It became a de facto standards organization without the formality of W3C. It's where we went to figure out what the future of the Web was," Ranganathan said.

Eventually, the Web-application direction won over the W3C. "Some things are clearer with hindsight of several years. It is necessary to evolve HTML incrementally," said Web founder and W3C Director Tim Berners-Lee said in 2006.

But Berners-Lee at the time also maintained the commitment to the "well-formed," more rigorous XML-based future: "It is important to maintain HTML incrementally, as well as continuing a transition to well-formed world, and developing more power in that world."

In practice, the W3C world and WHATWG world involve many of the same people. That probably eased the reconciliation to the current state, where WHATWG and W3C operate simultaneously, the first more informal and the second with more careful handling of intellectual property concerns.

Ultimately, HTML carried the day. What began with interest in more sophisticated Web sites such as eBay blossomed with the arrival of Ajax, which used JavaScript to build more sophisticated Web-based applications. And Web applications weren't just theoretical ideas.

"When Gmail and Google Maps and Ajax came along, it became really clear we needed a new set of technologies that made it easier to make those kinds of applications," Smith said.

The transition culminated with W3C's bare-bones news last week: "Today the director announces that when the XHTML 2 Working Group charter expires as scheduled at the end of 2009, the charter will not be renewed. By doing so, and by increasing resources in the HTML Working Group, W3C hopes to accelerate the progress of HTML 5 and clarify W3C's position regarding the future of HTML."

Some features of XHTML 2 will be built into HTML 5, so the XHTML 2 work won't have been for naught, assuming a critical mass of browser makers do in fact include the necessary XML parser along the HTML parser.

HTML 5: no walk in the park
Though the W3C-WHATWG dust has mostly settled, the standard is far from finished, and indeed looks a long way off.

The present approach involves a give and take between browser makers trying out new features and the standards group codifying them. Features can't make it to the ultimate W3C state, "final recommendation," until at least two browsers support the feature compatibly, Smith said.

In practice, that means adventurous Web developers who choose to support the new technologies in effect are blessing them even though the technology might well change.

HTML 5 elements came from all over. Canvas, which involves two-dimensional graphics, began at Apple's Safari and now has won over Opera, Firefox, and Google's Chrome. ContentEditable, which lets Web pages be edited in place, came from Microsoft. Google now is working on a faster communication feature called Web Sockets. Programmers for WebKit, the open-source project underlying Safari, are developing DataGrid, which brings spreadsheet-like tables with sorting and editing to Web pages.

"The speed of the web is continuing to pick up in general," Barzdukas said. HTML 5 feature support figures prominently in the browser sales pitches from Google and from Mozilla, with its "upgrade the Web" tag line for Firefox 3.5.

Actual standardization, though, remains distant. Mozilla's Ranganathan hopes for drafts of some HTML 5 elements this year and a draft of the full specification in 2010.

The HTML 5 built-in video situation is illustrative. Hickson, the HTML 5 editor and now Google employee, posted a lament about HTML 5 video last week because browser makers don't agree on whether to support the patent-free Ogg Theora format, preferred by Opera and Mozilla, or the commercially popular H.264 format, preferred by Google and Apple. The upshot for now: HTML 5 is trying to standardize video but doesn't specify which format to be used.

That pace of HTML 5 standardization important, given the importance Microsoft places on supporting actual standards and the company's commanding market share.

"The support of ratified standards (that Web developers) can use is something that we are extremely supportive of," Barzdukas said. "In some cases, it can be premature to start claiming support for standards that are not yet in fact standards."

Mozilla is exhorting users to "upgrade the Web" with Firefox 3.5 and variations on that better-browsing theme can be found with Google's Chrome, Apple's Safari, and Opera.

The hope is that the Web will evolve from a series of relatively static pages to a lively home for Web applications--everything from today's e-mail to tomorrow's spreadsheets. But it could take awhile for reality to catch up with the vision.

It's indeed a bright, shiny future for browsers, and the avant-garde is advancing rapidly. Web developers eager to invigorate their Web sites or build fancy Web applications have to reckon not only with the massive, slower-moving army of ordinary Web browsers, but also with inconsistent support for the latest technology.

Browsers of the future
Many of new browser features stem from HTML 5, the still-not-finalized next iteration of the HyperText Markup Language standard that defines how Web pages are described. HTML 5 has spurred the arrival of built-in video and audio, local storage that Web sites or applications can use, "Web workers" that can perform background processing tasks for a Web application, drag-and-drop for better user interfaces, and other technologies.

Adobe Systems released on Monday beta versions of three programming projects for producing online applications that run in its Flash Player, software that's widely used but also under competitive threat from other Web technologies.

First is a beta version of Flash Catalyst, a programming tool that's meant for the designer crowd rather than the coding crowd. Catalyst lets designers create a Flash application's user interface in Adobe's Photoshop and Illustrator applications, import the files, attach a variety of actions to user interface elements, then produce the Flash application for production or for handing off to more serious programmers.

Second is the beta of Flash Builder 4, the harder-core programming tool previously called Flex Builder. This tool, based on the Eclipse programming software, employs Adobe's open-source Flex framework for building advanced Flash applications and is for the serious programming set who works in an integrated development environment (IDE). For example, it can be used to link Flash applications with a variety of back-end data sources for advanced features.

Third is the beta of Flex 4 framework that provides underpinnings for Flash applications, including everything from user interface components to animation technology. Flex 4, code-named Gumbo, is an open-source project.

Flash got its start as a way to produce animations on Web sites, leading to gripes that its timeline-based view of the world was alien to programmers. For the animation-oriented set, Adobe still offers its Flash Professional software, but for others, Adobe has the Flex-based approach for producing Flash applications.

Adobe offers a variety of tools in an attempt to appeal to a variety of programming styles. A single project can bounce among different people using the different tools, said Steven Heintz, principal product manager of the Adobe Platform business.

"We've really made all these tools work together," Heintz said. "For pieces of the same project, you can use the tools best for the job. We believe this is better than jamming all this together into one massive tool that's totally inappropriate."

Flash faces a number of challengers. Most directly is Microsoft's Silverlight, version 3 of which is set to be launched July 10. But Google, Yahoo, and browser makers also are advancing what can be done directly in Web browsers without relying on plug-ins such as Flash or Silverlight.

And HTML 5, an still-in-progress revision of the Hypertext Markup Language used to describe Web pages, comes with a variety of features such as the ability to run multiple tasks at the same time and to play video and audio as easily as browsers can display images today, and Google, Apple, Opera, and Firefox developer Mozilla are pushing what can be done with the JavaScript language for programming Web pages.

Adobe argues that it's got consistency on its side with Flash, though. Web users tend to upgrade to the newest Flash player relatively rapidly, and Flash works consistently regardless of which browser it's plugged into or which operating system it's running on. For programmers in the HTML camp, Adobe offers its DreamWeaver development software.

In contrast HTML and JavaScript--including advanced JavaScript applications built with technology called Ajax--varies from browser to browser, said Shafath Syed, a product marketing manager with the Adobe Platform group.

"We've come full circle" in the browser market to the mid-1990s browser wars, with different interpretations of standards and new features and differing support for that technology, Syed said. "That's always a challenge."

Another challenge both camps face is spreading to the increasingly important realm of mobile phones. Flash, for example, doesn't run on Apple's iPhone and is still under development for phones based on Google's Android operating system. Those devices support JavaScript and some HTML 5 features, though, they, of course, lack much of the processing power and memory to make full use of it.

The Adobe programming tools also can be used in the production of applications that run on AIR, the Adobe Integrated Runtime that lets Flash applications run on their own outside a browser.

A new developer version of Chrome takes some significant strides to adding the top-requested feature--the ability to accommodate extensions that customize what Google's browser can do--but programmers also pushed back support for a collection of significant advanced Web features.

Google Chrome 2.0.180.0 emerged Tuesday night for people willing to try the developer preview version. The new version installs some of the plumbing necessary to support the feature, according to the release notes.

"The extensions posse would like to point out that as of today's dev channel release, extensions are starting to be a bit more useful. We can now put little bits of UI (user interface) in the chrome of Chrome, and some of the APIs (application programming interfaces) are starting to come together," said Google programmer Aaron Boodman in a mailing list post Tuesday. "There is still quite a ways to go, but if you're interested in building extensions for Chrome, this might be a good time to start taking a look."

Extensions are a big advantage Mozilla's Firefox has over rival browsers, not just because the browser supports them but because thousands are available.

A lightweight sample Chrome extension shows how many Gmail messages you have.

(Credit: Google)

Google also updated its extensions how-to page and provided some sample Chrome extensions. To use extensions, people must launch the browser through the command line with the "--enable-extensions" option.

Extensions work has begun. Cleeki has a Chrome extension, for example, that lets people select a word and then perform various actions with it such as searching for it without leaving that page.

The new version also lets you allow pop-ups from a specific Web site, fixes a few bugs, and upgrades to the latest versions of two major components, WebKit for rendering Web pages and V8 for handling JavaScript.

At the same time, though, it looks like more waiting for fans of a handful of new features arriving in HTML 5, the upcoming revision to the Hypertext Markup Language that's used to describe Web pages. Chrome developers had planned support for several HTML 5 features in a forthcoming main incarnation of Chrome, version 2.1, but now they've been pushed back to 3.0. (That's still a ways out: Even version 2.0 has yet to arrive in Google's mainstream "stable" version of Chrome.)

The HTML 5 features pushed back include the following:

• Local storage, technology for storing information on a person's computer. That's good for using your Web-based e-mail system while offline, storing browser extension preferences, and other more sophisticated aspects of Web usage.

• Video support that permits easier embedding of video on Web pages and better integration than is possible with current video technology such as Adobe Systems' Flash.

• Web workers, which let a browser perform processing chores in the background. This technology enables more sophisticated Web applications that can get work done without bogging down the user interface.

A Chrome programmer noted the change in a terse note Wednesday. "Moving out of Mstone:2.1 (milestone 2.1) as there just isn't enough time to work on this issue," said a Chrome programmer in a status update note about the local storage feature on Wednesday.