Good stuff by Andy Clarke. I would suggest if you can’t live with these browser differences, you’re not really understanding the way modern CSS is supposed to work. Visit site »
I totally agree with Andy that it makes a lot of sense to show clients HTML/CSS/JS prototypes rather than static visuals, but I’m not sure how to reconcile this with the needs of our clients, as well as our resources at Blue Flavor. For us, the trouble with interactive prototypes is twofold:
In short: I totally agree with Andy, but saying “we should do interactive prototypes instead of static design visuals,” is the easy part. Figuring out how to actually make that work within your business model is harder. If you can pull it off, awesome. Visit site »
Andy says that Opera’s latest filing against Microsoft is evidence that the CSS Working Group (which contains mostly representatives of the various browser manufacturers) must be disbanded and a new strategy put into place — one which includes more representation from designers and developers.
I’ve written about this before, so obviously, I generally agree with the general principles. However, I’m unsure what motivation browser makers would have to implement standards if they were less involved with creating them. And, quite frankly, I’ve pretty much give up on the idea of the W3C as a relevant body in our industry. The W3 basically feels to me like the 55 year old store manager who has been working at your local WalMart for 30 years. He’s slow, old, tired, obsessed with policy and procedure, and resistant to change — people just kind of let him think he’s in charge while the rest of the company moves on around him.
Bottom line: I generally agree with Andy, but I see no reason to believe a change will ever happen. Visit site »
Who knows if he was being light-hearted or mean-spirited, but I found it freaking hilarious. Visit site »