Around the Browsersphere #14

Posted on January 1st, 2010 | 2 Comments »

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

Chrome

Firefox

Internet Explorer

Opera

Minor Players

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

Happy New Year, everyone.

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

Microsoft to Offer Browser Ballot Screen in Europe

Posted on December 16th, 2009 | 3 Comments »

The big news in the browsersphere today is that European regulators have dropped their antitrust case against Microsoft after the company agreed to offer European users of Windows a “ballot screen” allowing them to choose from 11 alternate web browsers.  Internet Explorer will continue to be an option, of course, but the following browsers will also be available as choices for the users:  Firefox, Safari, Chrome, Opera, AOL Explorer, Maxthon, K-Meleon, Flock, Avant Browser, Sleipnir and Slim Browser.

For more on the stipulations of the deal, be sure to read the coverage from The New York Times (via @MaxthonNews).

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

Safari Not Represented on Twitter?

Posted on December 13th, 2009 | No Comments »

The Good News

As a follow-up to publicizing the @Browsersphere account on Twitter, I’ve created a new Twitter list for following all of the major web browser vendors:

@Browsersphere/web-browsers

The Bad News

Unfortunately, it looks like Safari is not represented officially on Twitter.  What’s up with that?

And no, I don’t consider @AppleSafari an official account:

twitter_applesafari

;)

Tags: ,

Twitter Watch #3

Posted on December 13th, 2009 | 2 Comments »

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.

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

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

Geolocation API Support Coming to Safari

Posted on April 8th, 2009 | 10 Comments »

A couple weeks back, Opera made headlines when it released a browser build supporting the Geolocation API as specified by the W3C.  That prompted Ars Technica to write an article summarizing current Geolocation API support, which mentioned that both Opera and Mozilla (more on the Firefox implementation can be found at Mozilla Links) have released browsers supporting the API.

Now it appears that Safari will soon be supporting the Geolocation API as well.  In documentation that appears to have gone out to iPhone developers regarding new features in iPhone OS 3.0, the following appears:

Safari…supports the Geolocation JavaScript classes, which work with the onboard location services to retrieve the current location of the device.

A Google search for “safari geolocation” doesn’t really turn up much useful information, but it’s obvious from existing WebKit bugs that the feature has been getting some attention as of late.

It’s going to be interesting to see how prevalent the use of this API by web developers becomes as more of the major web browsers add support for its functions.

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

Apple Releases Safari 4 Beta

Posted on February 24th, 2009 | No Comments »

I accidentally stumbled upon the fact that Apple released Safari 4 Beta today. According to some of the early feedback I’m seeing, along with a post from ITworld, it sounds like the beta is reminding a lot of people of Chrome. I’ve yet to download it and try it out, but I wanted to pass along the word that it’s out there, in case you want to give it a try. I’ll be posting more on the new browser release when I’m back from vacation and have some more time to form my own opinions about it.

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

Opera Widget Keeps You Up-to-Date on Browser Security

Posted on July 12th, 2008 | 2 Comments »

An article titled Check the Security Status of Browsers with Opera Widget reads a bit like something coming directly out of the Opera marketing department.  The article covers an Opera widget called Stay Secure that refreshes based on the latest data from Secunia every hour to show you a graph like the following indicating the security levels of Internet Explorer, Firefox, Opera, Safari and Konqueror:

Example of Stay Secure Widget

I say the article reads a bit like a release from the Opera marketing department, because assuming Opera views Firefox as a competitor, the widget screenshot shown in the article and statements like “the test showed that Firefox 3 was [the] most vulnerable one and Opera the least” seem a little biased.  Was this actually a test, or did it happen to be the state of security at that moment the screenshot was taken?  For example, above it looks like Internet Explorer and Konqueror are the two most vulnerable.

Regardless, it seems like a neat little widget for those who like to follow web browser security closely, as long as you’re willing to use Opera to track it, since the widget is Opera-only at present.  For those like me who dabble among various browsers, this isn’t an issue.

Anyone know of similar features/extensions for other web browsers?

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