Category: browsers
From the market leaders to the up-and-comers; news and opinion on browsing software.
From the market leaders to the up-and-comers; news and opinion on browsing software.
Mozilla’s Chris Double has announced on his blog that he’s implemented the (proposed) HTML5 <video> element in a build of Firefox (demo screencast). The element will natively support OGG Theora files.
While I think this is great news and has a lot of potential, I foresee one major obstacle to this becoming standard: proprietary codecs. If they decide to implement it, Apple will want Quicktime in Safari, and Microsoft will want Windows Media Video in Internet Explorer.
As one commenter notes, the idea will be to have fallback options for anyone who doesn’t have an OGG player, probably in Java; there are some examples of how this will work on the Wikipedia Video page (caution: this caused Firefox on OS X to crash, although Firefox on Ubuntu played it perfectly).
Theora is obviously the most common-sense cross-browser, cross-platform, non-proprietary solution; but since when has the internet been governed by common sense?
Update: Since writing this post, I’ve found out that Opera also has an experimental implementation.
The developer of Swift, the browser that was set to be the first native to Windows to use the WebKit rendering engine, has announced that development with WebKit is to be halted as the Windows port is unstable, and future versions will be based on Mozilla’s Gecko engine until WebKit stabilises, at which point Swift will switch back to it.
So I have to ask: what will Swift bring to the table without WebKit? We already have a bunch of Gecko-based browsers, and we have no information about what features Swift will implement.
I was pretty enthused when Swift was announced; even if it just had basic functionality, the fact that it was based on WebKit was pretty exciting. But as we’ve seen just two rudimentary pre-Alpha releases in almost 10 months, and no roadmap or project information is available on the website, this is turning into vapourware for me.
Remember the bad old days of “This site is best viewed with Browser X at Resolution Y”, before the concerted push towards web standards? Looks like they could be on their way back.
Now, I kind of understand their problem; they don’t want to have a whole load of websites appear broken when users upgrade to a new browser. But they’ve got their view of responsibility around the wrong way: site authors should have to opt out of standards in order to support IE, not opt in.
Looking through the popular links on del.icio.us I found a page of tips for CSS: CSS Hacks & Issues.
Most of the tips are useful, if a little familiar by now, but their first one bugged me: Browser-Specific selectors. As you’ve probably inferred, it shows you how to use CSS hacks in order to provide browser-specific code. My problem is this: many people – myself included – think you shouldn’t use CSS hacks.
It’s an ongoing argument, but certainly in the case of Internet Explorer there’s no need for hacks when you can use conditional comments.
I think that if you’re teaching how to use CSS hacks, at the very least you should be linking to the arguments against their use.
Mozilla have released the latest Alpha of Gran Paradiso, the developers preview of Firefox 3. This release contains no interface overhaul, but introduces a number of new features:
I’m back from my holiday, with a quick look at some of the links I would have discussed in more detail had I been here…