#chrome

From Chrome 131 you have more options to style the structure of <details> and <summary> elements. You can now use these elements when building disclosure or accordion widgets.

If only Firefox was 3% better things would be so different... or would they?

After perhaps a hundred re-installs of Linux, countless hours reading Stack Overflow posts, and a roller coaster of triumph and failure, I’m proud to say that we’ve landed on an Ubuntu installation script that meets our needs and makes it trivial for us (or you!) to create a Codestarter laptop.

Firefox today reminds me of Firefox when I first discovered it. Mozilla has once again delivered a technically superior product while completely respecting my rights as a user. Firefox is freedom.

Firefox today reminds me of Firefox when I first discovered it. Mozilla has once again delivered a technically superior product while completely respecting my rights as a user. Firefox is freedom.

Google Chrome for iPhone and iPad is here. But as you all know by now, it is not the complete Chrome experience on iOS. There are many compromises (platform limitations, as Google calls it) that Google had to make to bring Chrome to iOS. Let’s take a look at 7 of them.

Google Chrome for iPhone and iPad is here. But as you all know by now, it is not the complete Chrome experience on iOS. There are many compromises (platform limitations, as Google calls it) that Google had to make to bring Chrome to iOS. Let’s take a look at 7 of them.

First of all, we understand that this will be frustrating to extension developers, and our decision wasn't made lightly. We went to a lot of effort in the design of the extension system to make it possible for people to self-host. All of the formats and protocols involved in the extension system were made simple with the idea that developers could re-implement them. It makes us sad to take off-store install away.

GPG4Browsers is a prototype implementation of the OpenPGP Message Format [RFC 4880]. The implementation is currently written as Chrome Browser Extension with a Googlemail integration for encrypting, decrypting or signing emails.

A couple of interesting things happened in the world of Web browser usage during October. The more significant one is that Internet Explorer's share of global browser usage dropped below 50 percent for the first time in more than a decade. Less significant, but also notable, is that Chrome for the first time overtook Firefox here at Ars, making it the technologist's browser of choice.

"I see no reason why Chrome won't rise to above 20% in the short term. This means, of course, that the market share of Firefox and Internet Explorer will continue to drop. But as I noted some time back, this really isn't a huge problem for Firefox - although it is for Microsoft. The reason is quite simple: Firefox was never aiming at world domination, it was fighting to create an open Web where no browser held such a dominant position that it could ignore open standards and impose de facto ones instead. We pretty much have that now, with Internet Explorer increasingly standards-compliant - and proud of it, amazingly."

"It's a hefty wave to catch, but our browser has already been Atlas for five years - the IGB is perched atop a custom-written HTML parsing and rendering system. While a noble technical endeavor, this leaves to us the tasks of upgrading and extending the IGB to match the ever-shifting currents of the HTML standard. Hardly the best way for us to serve you, the player! But, like Atlas, we now have two Pillars upon which to rest these burdens. The first, and undoubtedly greatest, is the Heraclidean support provided by Awesomium and its Prince of Code. This library harnesses the raw strength of the Chromium browser toolkit - the muscles, knit from Webkit, that writhe cobra-like beneath the skin of Google's Chrome - and hand-delivers rendered HTML pages to us as nice 3D surfaces, which we can then readily display in our own Trinity engine."

"For a long while now (even before Google Chrome was announced), Mozilla has been examining ways to make Firefox better by splitting the work of displaying web pages up among multiple processes."

"The fun comes when I kill -9 this gecko-iframe, the “tab” containing mozilla.com. To the non-geeky, invoking kill -9 on a program causes it to crash IMMEDIATELY. This simulates what would happen if, say, you tried to run a buggy plugin and it got itself into trouble. Notice that only the “content” disappears when the page crashes; the user interface itself keeps running as if nothing happened. This is a big step forward! If I were to kill -9 the current version of Firefox, everything would die, user interface and tabs."

"Today I gave a presentation at Google I/O explaining some of the cool ideas that lie at the heart of our upcoming extension system. For those who didn't get a chance to attend the conference, you can check out the slides"

"Although Stainless started out as a technology demo to showcase our own multi-processing architecture in response to Google Chrome, we've been inspired by our growing fanbase to forge ahead and craft Stainless into a full-fledged browser. In fact, Stainless now has features you won't find in Chrome or in any other browser."

"hough Firefox remains the leader on the SunSpider test, with a score of 2,110, Chrome edged very close with 2,140."

"Reading the Google Chrome comic strip made clear the parallel to the emergence of QEMM and DESQview: All today’s browsers are effectively single tasking, in that only one tab can be actively processing, say, a JavaScript application at any given time (”inherently single threaded”), yet the tabs are interactive to the point where the misbehavior of an “application” in one tab can impact — and sometimes crash — the operation of the entire browser. Web 2.0 has brought about an array of browser-based applications and activities that require a more robust, stable, multiprocessing browser with each process assigned to its own memory space and associated data structures — which is basically how DESQview operated. Indeed, when I pointed this out during yesterday’s SquawkBox, someone labeled Google Chrome as “DESQview for the cloud.” Talk about “Back to the Future“!"

"Of course, the huge design choice that isn't explained, the giant in the room, if you will, shows up in this illustration from the comic: ... I can't help but think that people will encounter some difficulties in using a browser that's taller than a man. The Fitts' Law hit alone seems worth a bit of rethinking on Google's part, at least without a lot of stretching."

"Chrome is the end of the browser and the beginning of the Cloud Client. These are quite different things. A Cloud Client is a flexible and configurable Interface in which an application can run. Whether the rest of the application is local or lives in the cloud is an option - and switchable. The user may not even know nor care. It doesn’t sound much like a browser does it?"

"So even in a more competitive environment than ever, I’m very optimistic about the future of Mozilla and the future of the open Web." John Lilly is the CEO of Mozilla.