Tag: Web

Posted on
by

Internet Explorer.My feed reader is filling up with commentary on Microsoft’s proposal to lock web pages to specific rendering engines (funny how it doesn’t sound quite so forward thinking when you put it like that). Rather than link to a lot of them, I’ll just link to Opera Watch’s post which collects quotes from various standards & browser people.

The IE7/IE6 ratio on this site is still holding above 1 for the month (yay!) at 33.6% to 28.3%.

Also interesting: last week we got our first visit from Internet Explorer 8. Just one visit to Katie’s analysis of Wolfram & Hart’s work comp liability, but it loaded the relevant images, styles, etc., so it looks like an actual browser visit (and not some bot using a fake UA, like the spambot that keeps trying to post comments as Firefox 9). More importantly, it actually came from an IP address that’s assigned to Microsoft and resolves to a microsoft.com hostname, so I think it’s the real deal.

Posted on
by

2008: Year of the Layout Engine – CSS3.info takes a look at the four major categories of web browsers, and where they’re likely to go this year.

Progressive enhancement is an approach I’ve been taking for quite a while, particularly with my personal sites, but it’s starting to creep into sites I’m building for work as well. Essentially: Build it to look decent in everything, but throw in enhancements to browsers that you know can handle them.

An example of progressive enhancement: the rounded corners on the tabs on my Flash site. They’re not critical to the design, but it does make it look better in Safari and Firefox. And in theory, Opera and IE will eventually pick up the capability. (Though in this case, since border-radius is still experimental, I’ll have to change the CSS when they do—so maybe it’s not the best example.)

Posted on
by

I’ve been meaning to post these photos for a while now, but with the discussion on Netscape’s impending doom, I should post them now.

Back in February, I was wandering the aisles at Micro Center and noticed a couple of odd software titles on the shelf:

  • Netscape Basics, a jewel-cased CD-ROM which contained Netscape Communicator 4.5 and boasted compatibility with Windows 95 and Windows 98.
  • Opera for Windows, a boxed copy of I forget-which-version, but judging by the “New! Voice Enabled!” badge, it’s probably 8.0.

Keep in mind that this was February 2007. So that was an 8-year old Netscape box, and a 2-year-old Opera box. Netscape had been free for 9 years, and Opera had been free for 1½ years.

Someone had sensibly marked the Netscape CD down repeatedly, ending with a price tag of $0.42. I was half-tempted to buy it just to prove that I’d found it, but decided taking a picture would be better, since it wouldn’t clutter up my desk. Incredibly, no one had thought to mark down the Opera box. They were still asking $39.99 for it.

Did I mention pictures?

Netscape Basics CD for $0.42 Opera for Windows for… $39.99

Posted on
by

NetscapeIt’s been a long time coming, but AOL has officially decided to shut down the Netscape web browser. The final security updates for Netscape 9 will go out in February, and then that’s it.

It’s been on life support for a while now, as AOL has tried repeatedly to revive it. After they dismantled the Netscape team in 2003 (just before spinning off the Mozilla Foundation), everyone expected that would be the end, but they came back with a surprise update, Netscape 7.2, the following year. Then they hired an outside company to reinvent it as a mash-up of Firefox and Internet Explorer, producing the Netscape 8 chimera. And just a few months ago, they went back to the well and released the Firefox-based Netscape 9, trying for the Flock model of integration with social networking sites…but only integrating with their own.

So what killed it? Netscape was arguably the pioneer, building on Mosaic’s success to create the first widely-used browser on the fledgling World Wide Web.

  • Internet Explorer being pre-installed on every Windows desktop
  • The commercial-to-freeware transition. Back in the 1990s, the only business model for giving away a free web browser was to subsidise it with revenue from other products. This led to selling the company to AOL, and opening the source code.
  • The missing Netscape 5. IE5 was considerably better than IE4, and arguably better than Netscape 4 in some areas. And Netscape didn’t have a new version to compete, because…
  • The transition to open-source took a lot longer than expected, leading to…
  • The disastrous Netscape 6. While there’s something to be said for meeting deadlines, Netscape 6 was a prime example of why not to release early. The program just wasn’t ready (Mozilla actually declared the code to be 0.6), and it turned off many users who might otherwise have stuck around a little longer for a stable release.
  • Fundamentally, though, AOL never seemed to know what to do with it. Is it a product? An exploitable brand name? A threat to brandish during contract negotiations with Microsoft?

FirefoxIt’s interesting that, as I made this list, I realized that the transition to open source really didn’t help Netscape, the company. But it led to the formation of the Mozilla Foundation and the release of Firefox, one of the most visible open source success stories out there. The company and brand name withered, but the code itself flourished.

Like the demise of IE/Mac, it’s more of a symbolic end than one of substance. In my opinion, the true “heir” so to speak of the early Netscape has been Mozilla, and now Firefox, for quite some time.

Update: Asa Dotzler has a somewhat less nostalgic take on the matter, as well as a link to commentary at TechCrunch. I can’t believe I forgot to mention the crippling/crufting of Netscape 6-7 as compared to Mozilla.

Update 2: More comments at Slashdot. Gee, I wonder who submitted that story? 😉

Update 3: Some commentary from the Web Standards Project, with a somewhat familiar-looking title.

(via Opera Watch)

Posted on
by

Internet Explorer.Okay, this will mean nothing to most people out there, but to web developers, particularly those who use standards-based design to maximize compatibility with different browsers, this is monumental.

An internal build of Internet Explorer 8 has passed Acid2.

The Acid2 test was released in April 2005 to test a number of pieces of the HTML and CSS standards that, at the time, no modern browser handled according to spec. The purpose of the test was to prod browser developers into improving their products, and to do so consistently, so that developers would have more tools available for cross-browser sites.

At the time, Microsoft dismissed its its importance entirely. Even though they were working on rendering improvements for IE7, they stated that Acid2 was not one of their goals. Meanwhile Opera and Firefox were both in the wrong phase of their development cycles to make sweeping changes, so Safari jumped on it and became the first browser to pass. (Every once in a while I see someone say Opera was the first, and I have to wonder where they were.) Opera followed with version 9, and the Firefox 3 betas pass it as well.

With Gecko (Firefox), WebKit (Safari), Opera and IE accounting for the four biggest web browsers and the most popular minor browsers (Flock, Camino, Shiira, etc., plus IE shells like Maxthon), this shows unprecedented convergence among clients. It will be much easier to develop a cross-browser website that runs on IE8, Firefox 3, Opera 9+ and Safari 3+.

There are, of course, many aspects of the specs that aren’t covered by Acid2. And there are emerging standards like HTML5 and CSS3. And there are plenty of other bugs, quirks, and extensions among various browsers (IE’s bizarre concept of having layout, for instance, trips up all kinds of weird issues). And then there’s waiting for IE8 to be released, and moving people up from IE7, not to mention all the people we still have to move up from IE6. Full benefit is probably at least 3 or 4 years away. *sigh*

(via WaSP Buzz)