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.
Aesthetics also provide a strong argument for web fonts. There are many beautiful and interesting fonts that can improve aesthetics and increase visual variety on the web. Just as I am sometimes stunned by beautiful book designs, I want to be overwhelmed by beautiful web pages. And, I don’t want those beautiful pages to be made up of background images.
HÃ¥kon Wium Lie has written another call for more attention to be paid to typography on the web. I’m in complete agreement; being limited to only a small handful of ‘safe’ fonts was okay for a while, as it made people think about the best way to present those fonts; it’s fast becoming a limitation, however – when we’re using images and Flash to get around the problem, it’s way past time to address it.
The two main arguments raised in the article against font embedding – rights restrictions and aesthetics – both have the same solution: responsibility. As a website maker, it will be up to you to use fonts that you have the right to use, and to use them in a way that doesn’t look like an explosion at a print factory. Legibility must still be the first rule of web typography.
All signs indicate Opera 9.5 will be the first browser to allow font embedding using the @font-face declaration; if so, it’s another good reason why there’s so much anticipation of its release.
A post called Trash All IE Hacks! on the (rather lovely) Web Designer Wall blog has attracted a huge amount of comments recently with its call to stop pandering to those who have the audacity to still be using the previous version of Internet Explorer (approx. 80% of visitors on one site I manage), and to display the broken layout as punishment for anyone not au fait with modern browsers.
Just in case you missed it, I was being sarcastic there; to take that attitude would be like a TV station transmitting black & white signals to anyone who hasn’t yet bought a High Definition set.
From the many supportive comments, a few said things like 85% of my time is wasted coding for IE6!
or I spent two nights getting the layout to work in IE6!
; to that, I can only reply: either you are doing something wrong, or you are a bad coder – or both.
It’s not hard to get sites to display properly in IE6; sure, you’ll have to put in a little extra effort, but it shouldn’t be anything like 85% of your time, or 50%, or even 10%. All you need to do is follow these five simple steps:
Recently I was chatting with Rapha Martins, and he mentioned a feature he’d like to see in CSS: a ‘default’ value for properties; that is, if you change the value of a property, a keyword that would change it back to the browser default rather than you having to specify that value again.
That has been proposed for CSS 3, with the ‘initial‘ value, and it’s been introduced into the latest preview of Firefox 3 (Gran Paradiso), with the browser-specific -moz- prefix. I’ve put together a quick couple of basic examples of how it will work (you will, obviously, need the latest preview to see them).
Update: There’s a more practical look at this subject in a later post, Using SVG in background-image.
If adopted widely, the use of SVG in <img /> and background-image could be responsible for some big changes in website design.
Take a look at this example of images in SVG (you’ll need an SVG-capable browser), which displays four photos at random positions and sizes on the page. Images could be pulled at random from Flickr (or wherever) and rotated, resized, and placed in the page as a background. Combined with multiple images, you could create layers of effect, almost like collages… pretty revolutionary.
div { background-image:
url('layer1.svg') left top,
url('layer2.svg') left top,
url('layer3.svg') left top;
}
It looks like Opera will be first to implement this feature with their 9.5 release, previews of which should be available soon. No definitive word on whether they’ll implement multiple backgrounds, but I’m hopeful.
KHTML and WebKit look set to unfork, and WebKit have recently announced a set of project goals (and non-goals), which include the statement:
WebKit is an engine, not a browser.
Which does beg the question: why is their blog called Surfin’ Safari, and prominently feature the Safari logo?
If you use Firefox and Chris Pedrick’s invaluable Web Developer extension, this should be very useful to you: 10 Things You May Not Know About the Web Developer Toolbar. I hadn’t seen the ‘View Color Information’ option before; it’s amazing!