Browsersphere

Google has unleashed extensions and their bookmark sync feature on stable builds of Google Chrome today.  If you’ll remember, the bookmark sync feature was enabled in Windows beta builds back in November, and support for extensions was announced for both Windows and Linux beta builds last month.  It looks like users of stable Chrome builds on Linux and Mac may need to wait a bit, still, however:

To those using Google Chrome on Linux, extensions are enabled on the beta channel. And for those using Google Chrome for Mac, hang tight — we’re working on bringing extensions, bookmark sync and more to the beta soon.

If you’re on Windows, you can either wait to be updated to the new build automatically over the course of the next week, or you can manually upgrade if you want to get your hands on the new features right away.

Once you’ve got the new build, you can head over to Google Chrome Extensions to start extending your browser.  Or you can head on over to the Google Chrome Blog to find out more about what’s included in the new build.

Tags: Beta, Bookmark Sync, Chrome, Extensions, Features, Google, Google Chrome, Linux, Mac, Releases

I ran across this photo today over on Flickr:

Courtesy of Flickr user KateMonkey.

Tags: Advertising, Chrome, England, Flickr, Google Chrome, Photos

We’re covering everything from the difference between Yahoo! Answers and Stack Overflow, to Firefox sabotage against IE8 add-ons, to Taco Bell marketing campaigns in this trip around the browsersphere.  Are you ready?

General

• This one is pretty funny, but maybe wouldn’t be as funny if it was true:  someone filed a Firefox bug claiming installing Firefox disabled his or her IE8 add-ons.
• WebKit received one of InfoWorld’s 2010 Technology of the Year awards for being a “tool for creating cross-platform smartphone development,” whatever that means.
• Yahoo! Answers, which is one of the most useless sites on the Internet, in my opinion, runs the gamut in attempting to answer the question “which language should I use to create a web browser?“
• Harry Parsonage went to great lengths to write a “forensics” paper on how privacy can be put at risk by various web browsers’ session restore feature.
• If you’re planning on attending MIX10 in March, Paul Scarpa of Spry Hive Industries is hoping to talk about the past, present and future of web browsers.  You’ll need to vote, though, to make that happen.

Chrome

• An article at Beet.TV claims that Google Chrome has reached 40 million active users worldwide since it’s initial beta release in September of 2008.
• Jim Lynch of ExtremeTech talks about why he switched from Firefox to Chrome on Mac.
• Dwight Silverman is using Chrome on Mac, too, and got pretty excited when a bookmark manager showed up in his build.
• If you’re a Chrome fan and an Ubuntu fan, you may like some of these Ubuntu themes for Google Chrome.
• Chrome’s Dev Channel was updated to version 4.0.288.1 yesterday across all platforms.  TechCrunch points out that the key features are those that showed up for the Mac platform:  bookmark syncing, the new “pin tab” feature, and most importantly, extensions.
• Unlike Yahoo! Answers, Stack Overflow provides a platform at which smart people can provide smart answers, such as this explanation of the difference between the browser process, the render processes and plug-ins in Chrome.

Fennec

• In a blog post that announces his transition from working on Fennec back to the desktop version of Firefox, Gavin Sharp also reveals how developing for Fennec was different than developing for Firefox, and introduces us to a few of the other major contributors to the new mobile browser.

Firefox

• John Lilly tweets about a theme/add-on combination that gives “glimpses of [Firefox] 4.0.”
• John Slater, Mozilla’s Creative Director, vows that Firefox marketing won’t go the Taco Bell route.
• Download Squad reports that Firefox 3.7 is showing some progress with its Windows 7 shell integration.
• Initial tests show that forthcoming multi-processor support in Firefox leads to a 3x speedup in JavaScript performance, but even that is still 50% slower than Google Chrome’s performance using the same test.

Internet Explorer

• Microsoft’s announcement that it had submitted a request to join the SVG Working Group sparked commentary from SitePoint and The Industry Standard.

Opera

• As you probably heard, Opera announced a new CEO this week.
• Opera is planning on releasing a browser beta for Windows CE and looking to find other niches after suffering losses of around $2 million during the last quarter.

The Minor Players

• “Digia @Web is a modern, fully finger touch controllable, web browser for mobile. @Web is currently available for S60 5th Edition and Maemo mobile devices free of charge.”  Techie Buzz has a review, which includes a screenshot.
• SRWare Iron Browser, which was mentioned here last month, has been reviewed, along with screenshots, over at GadgetMix.
• China is making some big investments in free software which could end up benefiting Maxthon.
• Flock 2.5.6 was released this week, fixing some integration issues with Flickr and Twitter.
• Reports from CES say that Ford has developed its own Web browser, which can be operated only while the car is parked (there’s more on the safety implications of related innovations in The New York Times today).  Left Lane reports that Ford’s browser is WebKit-based.
• This review of the Orca browser has plenty of screenshots for anyone who’s curious about the browser.
• Honza Pokorny, who you can follow on Twitter, has created his own browser, appropriately named Honza’s Browser, which you can try out on Linux or Windows.  He has also made the source code available.

Tags: Add-ons, Awards, Bookmarks, Bugs, CEO, China, Chrome, Digia @Web, Fennec, Firefox, Firefox 3.7, Firefox 4, Flickr, Flock, Ford, Gavin Sharp, Google Chrome, Harry Parsonage, Honza's Browser, IE8, Internet Explorer, JavaScript, John Lilly, John Slater, Mac, Marketing, Maxthon, Microsoft, MIX10, Multi-processor, Opera, Orca, Performance, Releases, Safety, Session Restore, SRWare Iron, Stack Overflow, Statistics, SVG Working Group, The New York Times, Themes, Twitter, Ubuntu, WebKit, Windows 7, Windows CE

Even though we’re venturing into edge case territory here, it’s nonetheless interesting to see how the four main web browsers compare when reduced to their minimum chrome, or browser window, size on Windows 7:

I’m not sure what’s more surprising, how large IE is at its most-minimized state, or how small Chrome is.

You can read more about the differences over at Softpedia.

Tags: Chrome, Comparisons, Firefox, Google Chrome, IE, Internet Explorer, Opera, Screenshots, Windows 7

I’ve been doing my best to keep my finger on the pulse of the browsersphere over on Twitter, but you know you’re not getting the real deal until we go “around the browsersphere.”

General

• In addition to needing an editor (”sometimes you a specialist”), Macworld may need to take a look at the latest browser market share figures.  They mention Chrome almost in passing while covering what some of the alternative browsers do better than Firefox and Safari.
• At a WebKit hackfest recently, some improvements were made to context menu handling, including the ability to hold the CTRL key while right-clicking to see the default context menu instead of any custom context menu provided by the current website.  Additionally, some include- and linking-related improvements were made to decrease the overall WebCore build time, which should come as good news to those 80 active WebKit committers.
• Avencius has some interesting thoughts on the competition between Mozilla’s Firefox and Google’s Chrome and suggests that, despite their lead in browser market share, the Mozilla folks should be worried.
• Some videos from Add-on-Con feature representatives for Chrome, Firefox and Safari and delve into topics such as browser security and mobile add-ons (via Dan Moore).
• Royal Pingdom takes a look at what 2010 has in store for the browsersphere.

Chrome

• In a LinuxCrunch review of the Linux version of Chrome (via Slashdot), it is touted as being “stable and fast,” but downsides such as lacking extension and RSS support are mentioned as well.  Additionally, there’s an interesting note about a KDE-related bug that Google has opted not to fix.

Firefox

• An article at TG Daily (via Digg) calls Firefox “clunky-looking” and says that the news Firefox 4 may not ship until 2011 “comes as some embarrassment for Mozilla.”  It goes even further to claim that Microsoft will now have a “clear advantage” over Mozilla and “bit-players” Chrome and Safari.
• An RC1 build of Fennec, the mobile version of Firefox covered here recently, was released tonight.
• You can get a feel for some of Mozilla’s plans for Firefox in the coming year over at Mozilla Links.
• If you long for the good-old-days of Netscape, you’re crazy the new Rebrand add-on may be right up your alley.
• If you’re experiencing some jumpiness with YouTube videos, The Firefox Extension Guru’s Blog has some tips on fixing the problem.
• Daniel Glazman has some thoughts on how notifications in Firefox could be improved.
• If you’re one of those “Danger is my middle name” types of folks, you can already start testing multi-process plugins in Firefox on Windows and Linux.
• As you may have heard, Firefox 3.5 is “the most popular browser in the world.”

Internet Explorer

• Tweak Internet Explorer with IE Tweaker.
• One Betanews reader wants Microsoft to “release [an] HTML5 and CCS3 compliant IE9 by June with a radically new UI.”
• FavBrowser.com points us to some videos from IE9’s JavaScript engine team, namely John Montgomery, Steve Lucco and Shanku Niyogi.

Opera

• In its coverage of Opera’s added support for CSS3 Transitions and 2D Transforms in the pre-alpha build of Opera 10.5, CSS3 . Info mentions that “Opera is the first browser to offer support for Backgrounds and Borders without the need for a vendor prefix, with Firefox and Safari still requiring ‘-moz’ and ‘-webkit’ [respectively].”
• With the pre-alpha release of Opera 10.5, Anne van Kesteren says “we are getting a little better at this iteration stuff.”
• A couple of articles (via Slashdot), Opera 10.50 Unveiled: Opera Is Once Again the Fastest Browser on Earth and Opera 10.5’s new Carakan Javascript engine is fast – Google Chrome fast, go into detail about the impressive performance of Opera’s new Carakan JavaScript engine (which I’ve mentioned here a few times in the past).
• True to form, Opera Watch has a solid rundown on Opera 10.5 pre-alpha as well.
• In reporting on Opera’s State of the Mobile Web report from November, TechCrunch relays that Russia is the top country for Opera Mini usage, but that usage is really growing in Asia and Africa.
• Even though I think it’s a cool feature (which admittedly takes some getting used to), FavBrowser.com lends a hand to those who want to turn off Opera 10.5’s tab thumbnails in Windows 7 (I’m sure this approach works for Safari as well).
• The Opera Core Concerns blog provides some details on Opera’s native support for JSON, including performance comparisons against the other main browsers.
• In Carakan Revisited, improvements made to the Carakan JavaScript engine over the previous Furthark engine are discussed, mainly focusing on garbage collection and caching.  The post also touches on some of the plans for future improvements.
• A New Year’s Eve post unveils a newer pre-alpha build of Opera 10.5 and discusses Opera’s new support for HTML5’s <video> tag.
• Introduce yourself to mouse gestures in Opera.
• If you’re excited about the pre-alpha builds of Opera 10.5, you can show it off with some wallpaper.

Minor Players

• SeaMonkey 2.0.1 was released as a security update this month.
• Now that Avant has been listed as one of the browsers to appear on Microsoft’s browser ballot screen, they need translation help.
• One Maxthon user thinks the browser is so cute that there should be a Windows 7 theme based on it.

There’s a lot more to cover, but that should hold you over until 2010.

Happy New Year, everyone.

Tags: 2D Transforms, Add-on-Con, Add-ons, Africa, Alternatives, Anne van Kesteren, Asia, Avant, Avencius, Carakan, Chrome, Comparisons, CSS, CSS3, CSS3 Transitions, Daniel Glazman, Delays, Development, Digg, Fennec, Firefox, Firefox 4, Furthark, Google, Google Chrome, HTML5, IE Tweaker, IE9, Internet Explorer, John Montgomery, JSON, Localization, Macworld, Maxthon, Microsoft, Mouse Gestures, Mozilla, Multi-process, Netscape, Notifications, Opera 10.5, Opera Mini, Performance, Reviews, Russia, Safari, SeaMonkey, Shanku Niyogi, Slashdot, State of the Mobile Web, Steve Lucco, TechCrunch, Twitter, Vendor Prefixes, Videos, Wallpapers, WebKit, Windows 7, YouTube

An article written nine months ago, The genius behind Google’s browser, goes in-depth with the main programmer behind Google Chrome’s v8 JavaScript engine, Lars Bak.  Although the article’s title and certain parts of the story perhaps give a little too much credit to one man (there’s a lot more to Google’s browser than its JavaScript engine), it’s a very interesting read nonetheless.  The following is a short excerpt from the article:

Many computer programs are built using previous versions, or related code, but V8 was started from scratch – a blank slate. When I meet [Kasper] Lund later in my Denmark trip, he takes great delight in underscoring this fact: “It’s the purest form of coding there is.” [Lars] Bak clearly agrees – as Lund speaks, he can’t stop smiling.

Beyond detailing the story behind v8’s development in Denmark, the article gives a personal glimpse at its key creator, something his Wikipedia article doesn’t quite achieve.

If you’re interested in the developers behind the browsers or browser-related technology you probably take for granted on a daily basis, I’d definitely give the well-written The genius behind Google’s browser a read.

Tags: Chrome, Developers, Development, Google, Google Chrome, JavaScript Engines, Kasper Lund, Lars Bak, V8

I’m all for raising privacy concerns, as long as it is done well and responsibly.  However, this morning I stumbled upon a gem of an article that tries to make claims about Google Chrome’s policies that simply aren’t true.  The sad thing is, the only research needed to deny the claims made in the article involves launching the browser and going to a URL.

In Chrome is not an Internet Browser and not open, but closed to the Internet’s Domain Name System, Scott Cleland, a self-proclaimed “prescient analyst,” claims that Chrome is “a gateway to Google’s datacenter to browse Google’s mirror copy of the Internet and track the user’s every movement.”  However, the two most incredible claims in the article are as follows:

• “Google’s Chrome browser effectively eliminates the Internet’s Domain Name System (DNS) address bar where a user can directly go to [a] URL.”
• “When one puts a URL, www.brand.com, into Google’s OmniBox search bar they do not go where they asked to go but to Google’s results page where Google can advertise against that brand without sharing the ad revenues with that brand, and where Google can offer competitors an opportunity to divert the user from their requested destination and to a competitor’s destination.”

The claims about Google’s “mirror copy” and bypassing the Internet Domain Name System are discredited point blank in a post from The Chromium Blog titled DNS Prefetching (or Pre-Resolving), which states “Google Chrome resolves domain names…using your computer’s normal DNS resolution mechanism; no connection to Google is used.”

That second bullet point, though, is the most easily discredited.  If you launch Chrome and type “www.starbucks.com” into the OmniBox, you are taken to www.starbucks.com.  You aren’t taken to a search results page and certainly don’t see any competitors offering their services along the way.  If you type only “starbucks” into the OmniBox, that’s a somewhat different story, but the article is making its claim about URLs, which is just flat out wrong.

Perhaps the most concerning fact among all these non-facts is that Scott Cleland is a consultant to Fortune 500 companies and an advisor to Congress! His bio states, “eight different Congressional subcommittees have sought Cleland’s expert testimony.”

He might as well have titled his article “Chrome bypasses the series of tubes.”

Tags: Chrome, Chromium Blog, Congress, DNS, Facts, FUD, Google Chrome, OmniBox, Privacy, Scott Cleland

To borrow from Pink Floyd, is there anybody out there?

Ironically enough, Browsersphere has been neglecting the browsersphere a little like Microsoft neglected Internet Explorer earlier this decade.  After all, my last post was way back in June.  However, unlike Microsoft, it isn’t the competition that has jolted this site back to life.  On the contrary, sites like Avencius and Twitter accounts like @AltBrowser have actually made me feel a little bit better about the whole ordeal, knowing that at least someone is out there covering the browsersphere in my absence.  Truth is, the site went dark out of pure laziness on my part.  Well, that and the fact that I’ve been pretty consumed by another project.  Nevertheless, I’m back, and after catching up a bit on what’s been going on, my first order of business is to share a little bit about what’s been tweeted in the browsersphere lately.  So let’s get to it.

• Looks like @ryan45419 is working on his own web browser named iSurfWeb.
• @humancell points out that Firefox and Safari accounted for 79% of all web vulnerabilities in the first half of this year.
• @ByteEye appears to be working on its own web browser as well.
• @erichthewebguy is happy to be seeing Firefox used more and more on TV these days.
• As someone who appears to have given up on Firefox for Chrome on the Mac, @lee_cummings may have coined a new term: “nozilla.”
• @UKTJPR wonders if anyone is willing to give up their web browser for a week.
• @DevJonny points out SRWare Iron, a browser created with the Chromium source code that apparently doesn’t have all the privacy concerns of Chrome.
• @BemusedWolf, who has come up with some colorful names for Firefox and Internet Explorer, might be interested in SRWare Iron.
• @SuperDuperCam had some colorful words to share about Firefox as well.
• @BrowserNews, the creator of the Dolphin3D browser, is touting it as “a better web browser.”
• @mrtech points us to a blog entry about what the Firefox team is doing about crashes and startup time.
• @usingpond wonders if Blackbird, which sells itself as an African American browser, is for real.
• @msacks makes reference to the Lobo browser, which is all-Java and uses a rendering engine called Cobra.
• @waynehastings and @deanq appear to be pleased with Chrome for Mac OS X, with the later giving a parting shot to both Firefox and Safari.
• @chrispy2004 appears to be displeased, however, claiming that Chrome for Mac OS X is the slowest browser he’s used in a long time.
• @GameFreak4321 doesn’t seem all that pleased either.
• @JasonTselentis thanks the “Facebook browser” for finally taking away Internet Explorer’s market share.
• @KileyG wonders what the threshold is for the number of open tabs before someone becomes unproductive.
• @muhanov discovers and shares the fact that the Android web browser doesn’t support FTP.
• @ganetsky wonders how it’s possible that no one has created a web browser named “Bowser.”  Good question!  Though to be fair, some people have referred to IE as the “Bowser” browser.
• @Andrew_James claims to be in “web browser heaven.”  I wonder if Netscape’s there.
• Both @jamienguyenle and @jinkhet refer to Chrome using sexual terms.
• @nicnab asserts that Firefox’s remembering of per-site zoom levels is enough to keep him hooked on said browser.
• @ConduitYourSite wonders what the best Twitter lists for browsers and web-related tools are.
• As I often have, @alex_crawshaw finds it ironic that you need to use a web browser in order to download an alternative one.
• @propstm wonders if IE6 users even realize what they’re missing out on, using such an out-of-date web browser.
• @derickthemacguy says Google Chrome looks like “a Fisher Price version of a web browser.”
• @souravghosh says that Mosaic “is considered the first browser to make the Internet easily accessible to non-techies.”
• @C_Hernandez_ heard that Camino is the fastest browser for Macs and apparently is going to check it out.
• @omegatron laments, as do many I’m sure, the fact that his mom doesn’t know the difference between a web browser and a web page.
• @Allyssen points us to a split-screen browser for the iPhone called iNetDual.
• @ericylai recommends the Bolt browser, which also happens to support a split-screen mode (check out the demo), for those tired of the default Blackberry browser.
• @IHtherapies finds KidZui, a web browser targeted at kids, very cool.
• Even if it’s “a bit slow,” Firefox is still @flyfiddlesticks‘ favorite browser.
• @abhishek tweeted about the Facebooker browser, which is currently available as a release candidate.
• @juandelpozo makes reference to Infinity Web Browser, a web browser for Android.
• @va3stl gave Midori a try.
• @wordtree likes the idea of trying a text-based web browser like Lynx.
• @tr4st recommends Lunascape, the “world’s first and only triple engine browser,” to web developers.
• @sphereinabox wants to know what mobile web browsers, other than Safari, support offline storage.  If geek.com is to believed, it looks like Fennec does, too.
• And finally, @rodhilton loves that Ubuntu lets him use a web browser while the operating system is still installing.

That’s it for Twitter Watch #3.  Believe it or not, Twitter Watch #2 was so long ago that I was still using Summize to search for tweets.

Before I end this post, since we’re on the subject of Twitter, I should mention that Browsersphere is now on Twitter as well.  Just follow @Browsersphere for real-time updates, links to new site content, etc.

Tags: Android, Avencius, Blackberry, Blackbird, Bolt, Chrome, Chromium, Cobra, Dolphin3D, Facebook, Facebooker, Fennec, Firefox, Google Chrome, iNetDual, Infinity, Internet Explorer, iPhone, iSurfWeb, KidZui, Lobo, Lunascape, Lynx, Mac, Microsoft, Midori, Mosaic, Netscape, Performance, Privacy, Rendering, Rendering Engines, Safari, Split-screen, SRWare Iron, Summize, Tabs, TV, Twitter, Ubuntu, Vul, Vulnerabilities

I learned via Twitter last Thursday that Google Chrome 2 had shipped, though you’d never know it from visiting the Chrome website.  As noted on the Google Chrome Blog on the day of release, “we’re referring to this as Chrome 2, but that’s mainly a metric to help us keep track of changes internally. We don’t give too much weight to version numbers and will continue to roll out useful updates as often as possible.”

However, with version changes come lofty expectations, and the release of Chrome 2 left at least one reviewer underwhelmed.  The good news is, hot on the heels of the release of version 2 to the general public, it was announced earlier today (hat-tip to Ryan Parman) that Chrome 3 has been made available to Chrome users on the “Dev channel” (which I’ve covered here previously).  However, with version changes come lofty expectations, and even users who are supposed to understand that “Dev channel” releases could potentially set your CPU on fire have been complaining about the audacity of Google to unleash a build with known issues on the “masses.”

I guess the Google Chrome team can’t win.  Regardless, if you’re like me and you like getting your hands on new web browsers that inherently seem to showcase improvements both under the hood and on the surface, you should be happy to learn that versions 2 and 3, if your stomach can handle it, are now available for public consumption.

Tags: Chrome, Chrome 2, Chrome 3, Google Chrome, Previews, Releases, Reviews, Twitter

While doing some web design brainstorming earlier today, I wondered if any progress had been made on adding support for CSS Gradients beyond WebKit, for which support was first introduced a little over a year ago.  Via MozillaZine, I realized I’m not the only one wondering this, and ended up stumbling upon the Bugzilla bug tracking the progress of CSS Gradients support in Firefox.  Reading through some of the commentary there, it gave me a newfound appreciation for just how fluid the implementation of these kinds of features really is.  For example, it’s somewhat obvious that the original support as announced at Surfin’ Safari was based on some of the canvas documentation related to HTML 5.

Paraphrasing the HTML5 spec and adjusting the language slightly to not be canvas-specific:

“The color of the gradient at each stop is the color specified for that stop. Between each such stop, the colors and the alpha component must be linearly interpolated over the RGBA space without premultiplying the alpha value to find the color to use at that offset. Before the first stop, the color must be the color of the first stop. After the last stop, the color must be the color of the last stop. When there are no stops, the gradient is transparent black…”

Furthermore, it’s obvious that not everyone completely agreed with the initial implementation, and it’s clear that Firefox developers collaborated with WebKit developers to hone in on a more logical implementation.

All of that being said, the reality is that CSS Gradients are not supported widely enough at the moment to be considered tools in the common web developer’s tool belt.  As aforementioned, Firefox support is still in progress (as of yesterday, in fact) and support in Internet Explorer 8 and Opera 10 appears to be non-existent, based on visits to this demo in those browsers.  The demo only seems to work as expected in Safari and Chrome (the latest “Dev” version, at least), which makes sense, since those are the major players that sport WebKit under the hood.

We’ll be keeping an eye on the progress of CSS Gradients support and several other, similar implementations over the coming year.

Tags: Bugzilla, Canvas, Chrome, CSS, CSS Gradients, Development, Features, Firefox, Google Chrome, HTML 5, IE8, Internet Explorer, Opera 10, Opera 10 Alpha, Parity, Safari, Safari 4 Beta, Web Development, Web Standards, WebKit