Tuesday, September 14th, 2010
CSS 3 Live: Progressive Enhancement
<p>From SitePoint comes a nice series of videos on CSS3, called CSS Live. Here’s one on Progressive Enhancement when using CSS3 features:Related Content:





Tuesday, September 14th, 2010
Category: CSS, Tutorial
, Video
Posted by Brad Neuberg at 7:00 am
4 Comments





Caching and dynamic views
My client does not want to change his cache settings on IE and I'm trying to figure out a way to dynamically update a view each time it is visited. I...
JQuery Function Not Defined?
In Episode 25, we chat about IE 8, standards, Acid3, server side JavaScript, and more.
Who are the ajaxians? Find out.
Please contact us at . We would love to hear about any news that we could put up here.
We have individual blogs too:
You can never tell enough about progressive enhancement to developers, thats for sure!
However the “Apple menu” in my opinion is not the perfect example… When I’ll show that result to my webdesigner, saying “Well…, and this is how it looks in Internet Explorer” he shalll say “Fix it, that’s not according design”. And he’s right, a solid gray menu can screw up the entire design.
Why even design a site when it’s not an issue if design elements are not rendered according design?
Why even embed the youtube video when you know it’s going to get cropped by this website’s layout? Perhaps it is time to consider redesigning so the content width in your posts is greater than 480 pixels.
croppy layout issues, just run these 2 lines of js in your browser’s firebug or webkit console as a temporary bandaid or just deal with it.
$(‘sidebar’).style.display = ‘none’;
$(‘maincontent’).style.width = ’700px’;
He seems to suggest that the same content looking diffferent across browsers is acceptable, even desired. If we’re talking laptop vs mobile, sure, to a degree. But if we’re talking about browser vs browser, there’s no way a web designer or a client will accept this. And rightly so.