|
|
|
While I agree that creating a consistent experience for every user in every browser (putting aside mobile platforms for the moment) is never going to happen for every project, I believe a near-exact cross-browser experience is attainable in many cases. As developers, our goal should not just be to get it working in every browser; our goal should be to get it working in every browser with a minimal amount of code, allowing future website maintenance to run smoothly.
Read more at www.smashingmagazine.com |
Our code couldn’t wait any longer to be free! But! This preview ain’t for the faint of heart! If you’re the bleeding-edge type and don’t mind a few scrapes and busted knees from time to time, feel free to give it a whirl.We’ve got interesting ideas in this thing. We want to know what we’ve done right how we could improve. And we’ve got a lot of work ahead of us!
Flock
This is a test post, blogged with Flock. Wonder where the tags I can fill in, will go. So far I’ve tagged bookmarks, sharing them at my del.icio.us account, which seems to work pretty well. At first it was terribly slow, but somehow it has improved.
Technorati Tags: test, flock
Update: so the tags are Technorati tags, and get added at the bottom of my post, right-aligned. Not too shabby if it weren’t for the fact I use a plugin for tagging. The post gets categorised in ‘uncategorised’, so that needs editing afterwards as well. Would be nice if in the future, one would get a dropdown list of categories.
Quick conclusion for now: it’s rudimentary, but it does work properly.
Update II: unfortunately it breaks validation. Before posting, my blog was valid xhtml 1.0 transitional. After this post, I get 9 errors.  /me runs off to fix …
There’s something that puzzles me. When you look at this comment with the browser encoding set to iso-8859-1 (as is the page itself), it doesn’t display properly. When you set the browser encoding to UTF-8, it does. Then, when I change the encoding for the page to UTF-8, it doesn’t display properly when the browser encoding is set the same but it does when the browser encoding is set to iso-8859-1. It really should be the other way around. When I don’t set the encoding, it displays properly but then my pages won’t validate as XHTML 1.0 Transitional anymore.
Then another strange thing: the name of Aine (which I now type without accent) is displayed properly both in the entry and in the sidebar (as one expects) but when I set the browser encoding to UTF-8, it’s displayed properly in the entry but not in the sidebar (which is inconsisten). You can see the difference in the sourcecode as well. In both cases I typed alt0193 so I don’t understand why it gets processed differently in each of the instances. Unless it’s something Movable Type does. But then it should do the same for the comment as well, no? *sigh*
|
|
|
July 24th, 2010 | 
