My last post was about using SVG values for the background-image property, and I pointed out one big problem with the technique:
The drawback of this is that it’s not ready for use just yet — browsers that don’t support SVG in
background-imagewill not provide any fallback, even if you supply anotherbackground-imagevalue; so in non-supporting browsers, no image at all will be displayed.
This was annoying me a little, and I couldn’t find any workarounds that didn’t use JavaScript. However, after a bit of head-scratching I’ve come up with a way to get around it.
While having a look through the list of features for developers planned for Firefox 4 earlier today, I noticed this:
You can now use SVG with the
imgelement, as well as the background image in CSS.
I know you can already use SVG in background-image with Safari, Chrome and Opera, and this, coupled with Internet Explorer’s push towards SVG and the strong chance this will be available in IE9, made me decide to take a closer look.
2008 was pretty exciting on the web, wasn’t it? The continuing rise of social media, mobile internet, APIs, frameworks… it’s getting harder to keep up with it all.
I won’t be so bold as to make any specific predictions about the year ahead — more of the same is my best guess! — but here are a few articles I’ve read recently which have an eye on the future.
One of the hardest things about Microformats is explaining their benefits to people. You can say “It’s a standardised format of marking-up content, which is both human and machine readable!” until you’re blue in the face, but until you can show people a practical benefit they usually remain unmoved.
Luckily there are a few tools out there which will help you show off the benefits of using Microformats, and involve little work from you.
While Firefox 3 is a really fast & usable browser, I was a little disappointed by the (comparative) lack of really new features in the rendering engine; that’s not to say there aren’t any, as there are plenty, but that Safari 3.1 and Opera 9.5 have set the bar very high in their latest iterations.
So that’s why I was delighted to hear about the 3.1 release of my favourite browser, and doubly delighted when I found out which features the team are planning to work on for inclusion in it:
Having missed the opening party, my introduction to London Web Week was last night’s Microformats vEvent. Unfortunately it wasn’t a good introduction, for two reasons;
First (and foremost), it wasn’t really about Microformats. The first speaker talked about RDFa and GRDDL, the second about RDFa and FOAF.
Second, the presumption was that we had an extremely high level of technical knowledge; a presumption that wasn’t true, in my case at least. I’m fairly new to Microformats but I have a pretty good idea of what they’re about; both talks went over my head anyway. And my poor wife, who’s learning about them for the first time, had no idea what was going on.
The description of the event said:
We hope that no matter your experience level, you’ll find the evening informative, enjoyable and inspiring.
I didn’t. In fact, it may well have been counter-productive for me; it took a subject I’m excited about, and made it sound complicated and boring.
I’m sure that some people would have got a lot out of it — the man next to me who’s studying for his pHD in artificial intelligence certainly seemed to enjoy it — but I think the organisers should have been more honest about the technical knowledge required, and saved some attendees a bit of time.
I did get a book for asking a question, however, so it wasn’t a total loss.
Usually when I attend @media (that is, on two previous occasions) I write a follow-up blog post on what I saw there. Well I attended this year, and I’ve written the post, but it’s on the blog of my employer, Preloaded: HTML5, Mobile, and UCD: what we saw at @media.
[#] 0 Comments