Browsersphere

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

As I mentioned on my personal blog recently, I’ve made the switch to 64-bit Windows 7 on my main home computer.  As someone who is used to using Google Chrome as his secondary browser, I was greatly disappointed when I found that Chrome doesn’t work on 64-bit Windows 7 out of the box.  Since making the switch to 64-bit back in March, I’ve been making do with Firefox, which I use as my primary browser, and Safari 4 Beta as Chrome’s replacement.  Both of those browsers work fine on 64-bit Windows 7, and in fact, there is even an x64 build of Firefox available, though I don’t use it personally because it feels too unofficial.

I decided to catch up on the issue today, though, hoping that maybe some progress had been made in getting Chrome working on 64-bit Windows 7.  A Google search on the subject led me to How to Run Google Chrome on Windows 7 64 bit Version, a post from the beginning of this year that apparently recommends opening up a security hole in order to get the browser to run correctly.  Luckily, though, since then, a couple of commenters have mentioned a much cleaner approach.  Paul, one of the site’s commenters, for example, recommends following the instructions in the Chromium Developer Documentation for updating to the latest “dev” version of the browser.

Upgrading to the latest “dev” build of the browser isn’t without its cons either, though.  In doing so, you are opening yourself up to any bugs or ill-conceived features that wouldn’t ever make their way into a normal, end user-oriented build.  However, for someone like myself who doesn’t mind playing around with risky builds, this is a small, acceptable price to pay for being able to run Chrome on my main computer.

Google refers to the upgrade process as “changing channels,” and the three available channels to choose from, using their Google Chrome Channel Changer, are:

• Stable: Official Google Chrome releases (~ quarterly updates)
• Beta: More stable releases (~ monthly updates)
• Dev: The latest features and bugfixes (~ weekly updates)

After using the Google Chrome Channel Changer to change my channel to “Dev,” the next step involved opening the web browser, selecting the “wrench” dropdown, and going to About Google Chrome.  Initially, though, I didn’t see anything about upgrading to a new version in that dialog.  I ended up having to leave Chrome open and idle for quite a few minutes, with the About Google Chrome dialog closed (though I’m not positive this was a requirement), before I opened it again and found that the browser had upgraded itself to the latest “Dev” version (2.0.177.1 at the time of writing).

To my delight, despite the fact that I’m still unable to run the default version of Chrome on 64-bit Windows 7, I am now running Chrome on my main computer without any issues.  In fact, I’m posting this from Chrome.

If you’ve found yourself in the same position and your mileage has varied, or even if it’s been similar, drop a note here and let us know.

Tags: 64-bit, Architectures, Chrome, Firefox, Google Chrome, Google Chrome Channel Changer, Safari 4 Beta, Troubleshooting, Windows 7, x64

Whoa.  Has it really been like eight months since the last time we went around the browsersphere?  Not good.  I guess we should do something about it…

General

• Lifehacker recently put the major players through some browser speed tests after some boasting by the Safari 4 folks.
• In Mobile Browser Wars, Ed Hansberry takes a look at the browser alternatives available for mobile devices (via Web Browsers News and Reviews).
• Ten Web Browsers that You May Have Never Heard of covers iRider, Lunascape, Ultrabrowser and Shiira, among others.

Avant Browser

• Avant Browser 11.7 Build 22, which appears to be a minor release, was released back on the 26th.

Camino

• Camino 2.0 Beta 2 was released back on the 27th.
• If you’re interested in the Camino schedule, get updated.

Chrome

• Read about improvements in the spellchecker used in Chrome.
• It is believed that extension support is coming to Chrome this May (via Web Browsers News and Reviews).
• See the first screenshots of Chrome running on Mac.
• Full-screen browsing has come to Chrome, but apparently doesn’t live up to the way the feature is supported in Firefox and IE7.

Firefox

• Daniel Glazman takes an in-depth look at monetizing Firefox extensions.
• A new mascot, Foxmosa, was recently added to the Mozilla family.
• Firefox Extension Guru’s Blog discusses the Firefox 3.1/3.5 release schedule and how advancements in other web browsers’ JavaScript engines have impacted the schedule.
• Some interesting file uploading ideas came up at a recent Firefox design lunch.
• Jesse Ruderman sheds some insight into the issues surrounding “continuous integration,” which from what I can tell involves how and when code is checked in and how build machines and tinderbox displays are impacted.
• John Slater, Creative Director at Mozilla, is looking for an intern.
• Take a look at the Mozilla Community Calendar.
• Firefox 3.0.7 was recently released.
• At first it was under consideration, and then the decision was made to version the Shiretoko release of Firefox, formally versioned as 3.1, as version 3.5.
• Here’s a granular look at the type of minor performance improvements that eventually make a web browser faster overall.
• Gotta love bugs that are simply titled things like “Make location bar autocomplete faster” and “Make location bar autocomplete even faster.”
• There is a call “for new Web apps that can help people make a difference while browsing the Web.”
• Is Firefox faster on Windows or Linux?
• Firefox is dominating in Antarctica.

Flock

• Apparently the Flock folks thought Flock would make a good Valentine’s Day gift?  Personally, I’m glad I didn’t heed their advice for my wife’s gift this year.   Though, it looks like the Flock folks weren’t the only ones with this bright idea.
• “People using Flock’s Eco-Edition conducted 80% more searches per user as compared to Flock’s overall population of users.”

Internet Explorer

• The Cost of Internet Explorer attempts to track all the “wasted time and effort” on the part of web developers trying to make websites compatible with IE.
• IE8’s Compatibility View explained (and a recap).
• IE8 Beta testers are making a difference.
• It’s not every day anymore that you see browsers like Internet Explorer 4 and 5.5 mentioned.
• An IE8 Reliability Update has been made available for Windows 7 users (like myself) who are using IE8 (unlike myself).
• It looks like the IE team will be pretty busy at MIX09.
• Check out a video that goes into detail about IE8’s new rendering engine (via Robert O’Callahan).
• Here’s a comparison between the 32-bit and 64-bit versions of IE7.
• Is the codename for IE9 “Triton?”
• Sarah Dutkiewicz wonders why Microsoft is held to a different standard when it comes to bundling IE with its operating system, Windows.

Maxthon

• Check out a chromed-out Maxthon icon.
• I think MaxthonGuy and I may have reached some kind of virtual truce.  That is, until the next time the madness reappears over at his blog.
• Learn how to use the custom search feature in Maxthon (via Maxthon Resources).
• A new version of Maxthon 2.5 was released recently.
• At least one Maxthon user is frustrated that his favorite browser isn’t included in the browser reviews found in PC magazines, etc.

Opera

• Avencius’ coverage of the Opera 9.64 release uncovers some details about some platform-specific code that should make Windows users’ browsing experiences more secure.
• Opera unveiled Opera Turbo last month at Mobile World Congress 2009 and it was later discussed at Opera Watch.
• Take a look at a speed comparison between the browsers developed for the Nintendo DS and the DSi.
• Similar to my recent post about various web browser vendors claiming ‘First!’, Choose Opera touches on the topic of whether it matters who developed a feature first or not.  Then, the very next day, they answered their own question.
• Opera Fingertouch is “a technology designed to make interacting with the Web easier and simpler on touch-based devices.”
• Apparently there is a demand out there for making Opera look like IE7 (via Daniel Glazman).
• Check out the Carakan FAQ for more information on Opera’s new JavaScript engine (via Opera Watch).
• Combining Opera with a touch UI.

Opera Mini

• Armenia, a country with around three million people, saw its Opera Mini usage grow by 2800% last year.  See this and other interesting statistics in the State of the Mobile Web report (via Choose Opera).
• “Yahoo! is expected to begin distributing Opera Mini via Yahoo! Mobile and also as a standalone download from Yahoo!’s mobile Web sites in the near future.”

Orca Browser

• The first build of Orca Browser 1.1, Build 1, was released back on the 25th.

Safari

• Avencius’ review of Safari 4 Beta is a very positive one, and some details regarding branding of the new JavaScript engine are ironed out in the comments.

SeaMonkey

• Read a draft of the new SeaMonkey vision (via Mozilla Developer News).
• SeaMonkey 2.0 Alpha 3 was released this past week.

Skyfire

• Skyfire 0.9 Beta was released back on the 12th.

There was a lot to cover this time around, and there’s much more I haven’t yet covered.  Hopefully that means we’ll see the 13th installment of “Around the Browsersphere” sooner than November.

Tags: Add-ons, Avant, Avencius, Beta, Bugs, Camino, Carakan, Chrome, Compatibility, Compatibility View, Daniel Glazman, Design, Extensions, Features, Firefox, Flock, IE7, IE8, IE9, Internet Explorer, Internet Explorer 4, Internet Explorer 5.5, iRider, Jesse Ruderman, John Slater, Linux, Lunascape, Mac, Market Share, Mascots, Maxthon, Maxthon 2.5, MaxthonGuy, Minor Players, MIX09, Mobile, Monetizing, Mozilla, Nintendo, Opera, Opera 9.64, Opera Fingertouch, Opera Mini, Opera Turbo, Orca, Performance, Releases, Rendering Engines, Safari 4 Beta, Schedules, Screenshots, SeaMonkey, SeaMonkey 2.0, Security, Shiira, Shiretoko, Skins, Skyfire, State of the Mobile Web, Themes, Touch, Triton, Ultrabrowser, Windows 7