Internet Explorer makes me sad every time I open it to cross-browser test during development and it crashes on console.log. A simple check OR define option can kill console in the IE developer toolbar, so I decided to write a more robust cross-browser compatible console.log.
There are a few Sass media query mixins going around for dealing with old versions of IE. Often they include predefined break points, whereas I like the simplicity of passing a numeric value. Capable browsers wrap the content in a media query, incapable browsers get the unwrapped content.
The HTML5 Boilerplate popularised the html tag conditional classes pattern. This pattern is usually some variation of: <!DOCTYPE html> <!–[if lt IE 7 ]> <html lang=”en” class=”ie6″> <![endif]–> <!–[if IE 7 ]> <html lang=”en” class=”ie7″> <![endif]–> <!–[if IE 8 ]> <html lang=”en” class=”ie8″> <![endif]–> <!–[if IE 9 ]> <html lang=”en” class=”ie9″> <![endif]–> <!–[if (gt IE […]
We’ve recently changed the way we do IE hacks at Soupgiant. For years we were using conditional comments to load separate CSS files.
Much of the time website owners & developers decide to drop IE6 support and they forget a key tenet of customer service: it has to be focused on the customer!
Increasingly I’m reading of web developers deciding to drop IE6 from their list of supported browsers, usually, because of its creative interpretation of CSS standards, besides IE7 is over a year old, and, IE8 about to be released.