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.
Apple have released Safari 3.1 for Windows and OS X (and Linux using Wine) today, and the feature that really stood out for me was the introduction of web fonts. Website makers have been bound to the same core fonts for years now, so suddenly having a huge palette to choose from is going to make an enormous difference!
Using them is pretty easy. First you have to declare the fonts using the @font-face rule – and, importantly, you have to declare each variant (weight, style, etc) individually by linking to the font file involved. You can’t just link to the directory and let the browser work out the variants. To see what I mean, take a look at this example (using Safari 3.1, of course!) and view the source to see the CSS involved.
Had the chance to run a few more tests to find out what’s new (and what’s not) in IE8. Good: @import media types seem to be implemented; Bad: XHTML still isn’t parsed, so everyone who thinks they are coding XHTML are still kidding themselves.
As just about everyone in the development community must know by now, Microsoft released a first Beta of IE8 today. I’ve been testing it for the last hour or so, and here are some notes I’ve made – the first of which is that this is really more of an Alpha than a Beta; there are a lot of bugs and errant behaviours.
One of the first things I noticed was that the browser comes with a limited set of development tools built in. They’re not well integrated, they’re not very extensive, and they’re not easy to use; but they’re there.
I am very pleasantly surprised. Microsoft have announced today that they have reversed their decision on the new standards mode trigger in IE8; instead of having to opt in to standards mode by using the META tag, you will have to opt out by using it instead.
In light of the Interoperability Principles, as well as feedback from the community, we’re choosing differently. Now, IE8 will show pages requesting “Standards” mode in IE8’s Standards mode. Developers who want their pages shown using IE8’s “IE7 Standards mode” will need to request that explicitly.
This is a very wise decision, IMHO (and I’m not the only one to think so). Standards-aware developers can code their sites to meet the latest standards in all the major browsers, and anyone who finds their site displaying strangely in the new Explorer can fix it with a small line of code.
Microsoft’s Interoperability Principles promise more open protocols and adherence to standards. I think this is a very welcome move, even if a small part of me is wondering what the catch might be…
Let me say up front that from what I’ve seen of Firefox 3 so far, it really looks to be a knockout browser; it’s light, fast, extensible, and the interface is flawless. The one and only thing that’s disappointed me slightly, however, is the lack of new front-end features for developers like myself to take advantage of.
Online applications have been given a huge boost with offline storage and new HTML 5 features, but where are the shiny graphical hooks for us to play with? Below are three new features I’d like to see implemented in Firefox 3.1 (which I’ve just made up).
NB: This might seem a bit previous, as Firefox 3 hasn’t actually been released yet, but I’ve been using the nightlies for a while and it seems unlikely that any of these features will be implemented before launch.
Is it possible that I’ve found a new IE bug, after all these years? And, worse still, a bug that wasn’t fixed in IE7? I’ve just spent half an hour looking for a solution, and I can’t find a single mention; surely someone has come across this before me?
It involves horizontal rules and the way they are displayed by Intenet Explorer, which seems to set a height limit that other browsers don’t. It’s probably easier if I explain it.