Overly-cute fox with puppy-dog eyes, captioned: Please don’t hurt the web. Use open standardsThe Mozilla Developer Center has just posted some desktop wallpaper promoting open standards, (and the MDC itself) with the theme, “Please don’t hurt the web. Use open standards.”

Apparently the design was a big hit as a poster at SXSW.

For those who haven’t seen it, the MDC is a great developer resource for web developers, describing lots of standards along with Mozilla-specific information.

(via Rhian @ SFX, who notes that the image is available for use under the terms of the Creative Commons Attribution-NonCommercial license. These wallpapers are also covered by the Mozilla Trademark Policy.)

Opera BrowserIn an interview at Opera Watch last week, Opera CEO Jon von Tetzchner responded to the eternal question: with less than 1% of global marketshare, why should web developers make the effort to support Opera? His response demonstrates another perspective on the numbers:

I believe we have something like 10 – 15 million active desktop users. That is actually quite a lot of people.

If you try to think about it, the place that I’m come from is Iceland. I was born in Iceland, that’s three hundred thousand people – we have a lot more. The place I live is Norway – we have a lot more. Actually if you look at it, the US has about 300 million people that live here, 50 states, about 6 million in each state on average. So which states have people that you would like to ignore?

He goes on to add that Opera Mobile is installed on 40 million mobile phones, with an additional 7 million people actually using Opera Mini. And then there are devices like the Nintendo DS and Wii…

Going by 2005 numbers, only four states have 15 million people or more: California (36M), Texas (23M), New York (19M), and Florida (18M). So take the 10–15M desktop users, the 7M Opera Mini users, and even 10% of the 40M mobile install base, and you’re looking at 21–26 million—the equivalent of the population of Texas.

Put that way, it doesn’t seem so small.

If you’re already supporting Firefox, in most cases the changes to support Opera 9 are minimal. The recently-launched Opera Developer Community has has tools, articles, and other resources to help build cross-platform sites.

Unless, of course, you don’t mind writing off a potential audience the size of Texas.

The Opera web browser has introduced a Dashboard-like Widget feature in Opera 9 Preview 2. I believe this is the first 3+ platform widget framework out there.

Dashboard is, of course, Mac OS X only. Yahoo! Widgets (formerly Konfabulator) is Windows XP and Mac OS X only. The KDE Desktop (mostly used on Linux and *BSD) has plans to include floating applets in KDE4’s revamped desktop, Plasma. Opera runs on Windows, Mac, Linux, and a number of other platforms.

Opera’s taken a very similar approach to Apple’s. A widget is a bundle of HTML, CSS, and JavaScript. The most obvious difference is the structure of the bundle: Continue reading

The new Opera 8.0.1 includes an experimental feature called Browser JavaScript. It’s a collection of client-side scripts that automatically corrects known errors on websites as they’re displayed. Opera downloads updated scripts once a week.

It’s an extension of the User JavaScript concept. Firefox’s Greasemonkey is basically the same thing, and it’s gotten a lot of attention as a method for correcting or enhancing sites. The key difference is that these scripts are centrally maintained, and automatically updated.

Browser JavaScript is disabled by default, and can be turned on by putting Browser JavaScript=1 in the [User Prefs] section of your opera6.ini file.

(via Opera Watch)

Via Weblog about Markup & Style:

Dive Into Mark provides an excellent example of why a browser shouldn’t second-guess file types.

Safari content sniffing for XHTML

It’s a screenshot of Safari looking at a text document… but the first line mentions XHTML, so it’s decided that’s what it must be. I’ve had lots of trouble with Internet Explorer doing the same thing, and Safari’s been aiming at bug-for-bug compatibility in order to “break” as few sites as possible.

[Edit: After the source blog was taken down, I grabbed the screenshot from archive.org and uploaded it here.)