Around the Browsersphere #15

Posted on January 7th, 2010 | 6 Comments »

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

Chrome

Fennec

Firefox

Internet Explorer

Opera

The Minor Players

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Around the Browsersphere #13

Posted on December 17th, 2009 | 1 Comment »

I debated whether or not I should skip ahead to #14, but I’m not really that superstitious.

General

Chrome

Firefox

Internet Explorer

Opera

The Minor Players

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

The Current State of CSS Gradients Support

Posted on May 8th, 2009 | No Comments »

CSS GradientsWhile 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: , , , , , , , , , , , , , , , , , , ,

Internet Explorer 8 Released

Posted on March 19th, 2009 | No Comments »

Straight from Twitter comes news that Internet Explorer 8 has officially been released today.  Early reviews seem to agree that IE8 is an advancement for Microsoft, but still not a big enough step forward to catch up with the competition.  You can form your own opinions by downloading the latest release from Microsoft’s site.

Tags: , , , , ,

Around the Browsersphere #12

Posted on March 7th, 2009 | No Comments »

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

Avant Browser

Camino

Chrome

Firefox

Flock

Internet Explorer

Maxthon

Opera

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

Safari

SeaMonkey

Skyfire

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: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Multi-process Web Browser Architectures

Posted on February 10th, 2009 | 2 Comments »

All the nonsense aside, now that it seems like multi-process architectures are beginning to surface in the world of web browser development, I thought it would be a good idea to dig in to the feature a bit and, at the very least, provide links to some useful information for those who are interested in what multi-process architectures mean for web browsers.

One of the more notable features included in the unveiling of Google’s Chrome was what Google refers to as “Crash Control.”  This feature allows for a “Windows Task Manager” type of interface for managing web browser processes.  Aside from providing the interface for explicit management of the running (or dying) processes, it is also meant to shield tabs within the same running instance of the browser chrome (for lack of a better word) from any issues arising in other concurrently running tabs.  In essence, when you accidentally load a web page in one tab that was developed using Microsoft Word, you don’t have to worry about the severe code bloat of the page bringing your other tabs to a screeching halt.  Or if the JavaScript of one page goes off into la-la land, you won’t necessarily lose any of the other non-offending tabs.

Months after this feature was unveiled in Chrome, it was announced as a feature of Maxthon under the name “The Isolator:”

Maxthon 2.5.1…includes a feature called The Isolator that separates the functions of each Web tab from all other tabs and other parts of the browser. The Isolator protects other tabs from also becoming frozen because a single unresponsive tab is monopolizing a computer’s resources.

Though it certainly wasn’t the first implementation (despite what MaxthonGuy might want you to believe), The Isolator is one of the first official implementations of a multi-process architecture among the web browsers that actually show up on the Browsersphere radar.  Unlike Chrome’s “Crash Control,” though, The Isolator is still considered to be “in advanced beta.”

Other than the press release, I wasn’t able to find much on Maxthon’s actual implementation.  On the other hand, there has been plenty of coverage on Chrome’s implementation.  Marc Chung, for example, does an excellent job of explaining Chrome’s process model.  He even goes so far as to show you how you can control the type of process model used by Chrome at launch time.  He also points to another interesting article from Chromium Blog that explains why Chrome uses the multi-process architecture and why the architecture is more relevant today than it was when web browsers were first created, and refers to a publication from which Chrome’s process model was derived.

Though the multi-process architecture has been heralded by many web users, it isn’t without its downsides.  Google Chrome Memory Usage – Good and Bad explains the trade-offs of separating tabs into their own distinct processes, including the following:

While the multi-process model provides clear robustness and performance benefits, it can also be a setback in terms of using the absolute smallest amount of memory. Since each tab is its own “sandboxed” process, tabs cannot share information easily. Any data structures needed for general rendering of web pages must be replicated to each tab.

For more information on Chrome’s implementation of the multi-process architecture from both a developer’s and end user’s perspective, I recommend checking out the following links:

And finally, here are some other multi-process-related links related to web browsers other than Maxthon and Chrome:

Tags: , , , , , , , , , , , , ,

Digg Watch #5

Posted on December 31st, 2008 | No Comments »

Let’s take a look at what web browser news has surfaced over at Digg over the past month:

And now for some bonus coverage from Slashdot:

Happy New Year, everybody.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

nth-child Support in the Major Players

Posted on July 12th, 2008 | 2 Comments »

After reading an article over at the SiteCrafting Blah Blah Blog about different ways to alternate table row colors, it occurred to me that the nth-child approach was not mentioned.  Way back in 2004 I had implemented a ridiculous (hindsight is 20/20) proof-of-concept around implementing tables without using the <table> tag.  However ridiculous the prototype might have been, one touch I added was the use of the nth-child pseudo-class to display alternating table rows in a different color.  Here’s what I wrote about that at the time:

This rule is actually a part of the CSS3 selector set, and if your browser was capable of rendering it correctly (I’m willing to bet it isn’t, at least at the time of posting) you’d see alternate background colors on the table rows (alternating between white and light gray).

Remembering that old proof-of-concept today, I decided to have another look at it.  I was disappointed to find that even in the latest version of Firefox (version 3), over four years later, the alternating row colors were nowhere to be found.  I was happy to see, though, that the latest versions of Opera (9.51 at the time of writing) and Safari (3.1.2 at the time of writing) actually do display the alternating table row colors.  As one might guess, IE7 falls in the Firefox camp on this one.

It’s unfortunate that only half of the major players support this useful feature, but I’m guessing we’ll see support added in Firefox 3.1, of which there is a first alpha targeted for release at the end of this month, since that particular release is meant to include a slew of CSS support geared toward Acid3 compliance.  Furthermore, one can hope nth-child support will show up in IE8, but that may be the least likely scenario between the two.

Tags: , , , , , , , , , , , ,

Digg Watch #4

Posted on June 22nd, 2008 | No Comments »

It’s that time again.  Since the last update, major versions of both Opera and Firefox have been released.  Only one of the two has been dominating in terms of Digg presence, though.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Twitter Watch #2

Posted on May 15th, 2008 | 1 Comment »

Last time around I used Tweet Scan, this time I’m giving Summize a try:

Tags: , , , , , , , , , , ,