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.
The W3C have announced that they have relaunched activity on HTML:
After the publication of HTML 4… W3C set forth to turn HTML into an XML-based format, called XHTML, due to the benefits of XML formats. The first full XHTML Recommendation was issued in early 2000. But due to the significant legacy of Web content that is some variant of HTML, traditional browser vendors moved slowly to adopt XHTML. This, in turn, has meant little motivation for content developers to adopt XHTML for the traditional desktop environment. Leaders in the Web developer and design communities therefore urged W3C to renew its commitment to HTML…
W3C is pleased to relaunch work on HTML with strong support from its Members and more staff resources (including people and hardware). W3C has tailored the HTML Working Group Charter to enable active participation from browser vendors, applications designers, and content developers, whose joint participation is key to the success of the future HTML.
A little while ago I claimed that SVG looks set to be the future of web graphics
, after Opera’s announcement that SVG would be allowed as a value in the background-image declaration.
Unfortunately Firefox won’t be doing the same with their next release; indeed, it seems that resources are limited at Mozilla;
With minimal resources available for SVG development, we need to make some tough calls regarding prioritizing development efforts in the Firefox 3 time-frame… This means that SMIL and SVG fonts will not make Firefox 3 with the current development resources, and the earliest chance for adding them will likely be in late 2008.
And a comment on the post confirms that the only way to implement SVG for the near future will be using the object tag. Looks like the future of web graphics is still a little way off.
A tiny but infuriating bug in current versions of Safari/Webkit is the one which treats any character after an apostrophe (or other special character) as the beginning of a new sentence. Not a problem that’s going to crop up many times, except when you use the text-transform declaration to capitalize a sentence.
Take this example:
It’s Apple’s Problem
Safari/Webkit users should see two capital S’s at the end of the first two words. Not the ideal solution. If you’re very concerned about your Safari visitors, you might end up not using this declaration at all.
This bug’s been identified for a long time – as long as Safari’s been available, as far as I know – and is still existent. Fingers crossed it will be gone when Safari 3.0 is launched.
15 CSS Properties You Probably Never Use (but perhaps should).
Most of these aren’t implemented in the IE browsers (do I even need to point that out?), many of them aren’t implemented in at least one of the other popular browsers, some of them are print-only.
Of the few cross-browser screen properties, probably the only one that I don’t use is clip – and honestly, I’ve never had a need to.
Something that’s been bugging me for a while, that I’d forgotten to write about; why does Firefox 2 on Windows and Linux have the classic Back and Forward buttons:

… while Firefox 2 on OS X has the crappy buttons?

If I’m not mistaken, FF2 beta releases on Windows had the crappy buttons, but were switched to the classic buttons after users complained. So why did the OS X version not switch too?
I’ve had to install a different theme on my Mac, as I kept hitting the Back History button by mistake. I use the GrApple theme instead.