Feeds

Getting your site sorted for IE 7

Just how bad will it be?

Securing Web Applications Made Simple and Scalable

After five years of tweaking the hacks that make your site look the way it's supposed to in IE 6, the CSS changes in Internet Explorer 7 are probably going to cause you some more pain.

Fixing bugs doesn't usually cause complaints, but the CSS bug fixes in IE 7 change behaviours web coders have come to rely on. Workarounds like the *HTML and underscore hack force IE to only parse the section of CSS you want it to; but they work because of bugs that are fixed in IE 7. In the best case, that won't matter. You put in the hack because the correct CSS that you've written for other browsers doesn't work in IE 6; the hack will still work for IE 6 visitors but IE 7 will parse the CSS intended for browsers like Firefox correctly and your site will still look good. Height, width and position bugs are fixed; you can scroll smoothly with JavaScript; and use CSS for transparency and hover effects without needing scripts.

There's a full list of changes in the IE 7 Readiness Toolkit, which will also check your code and let you know if there are any hacks that IE 7 will break. You can see the public bug database for IE 7 at Internet Explorer Feedback (apply here; irritatingly you need a Passport account to use it). You can sign up for the Application Compatibility Toolkit V5.0 Beta at the same site, which tests sites and add-ons for both IE 7 and Vista compatibility.

But not every layout bug is going to be fixed in IE 7. Current betas are layout complete, so if your code doesn't look right in the beta it won't improve in the final release. Rather than keeping the hacks you already have, Microsoft suggests rewriting them as conditional comments that lad the different styles needed for different versions of IE from a separate CSS stylesheet. You'll get the behaviour you want by calling it explicitly rather than relying on the browser parsing or failing to parse a line of code. If you're using hard-coded user agent strings that look for IE 6, at least change them to look for IE 6 or above, or IE 7 will end up with whatever fallback you put in to cope with browsers your user agent strings don't find (and if that's a page asking people to upgrade to IE 6, it doesn't look good).

You can also force IE 7 to render as if it was IE 6 by telling it to render your page in quirks mode, which has none of the fixes implemented in strict mode; compatibility mode will still render as if it was in IE 5. But that loses advances like rendering transparent PNGs, lighting up the RSS button if you have a feed on the page and offering your site as a search option if you're using OpenSearch 1.1. Painful as it may be, it's better to clean up your code.

If you're making changes to your site for IE 7, it's a good time to consider how much support you want to keep around for older browsers. IE 5 is in extended support as part of Windows 2000 and that goes on until at least June 2010, but IE 5.5 came out with Windows ME and it's now out of support, so you can expect business users to be moving away from it. By the same reckoning, after five years IE 6 is in extended support with Windows XP; but there are still plenty of users who aren't ready to make the jump to IE 7 (or Firefox). ®

Bridging the IT gap between rising business demands and ageing tools

More from The Register

next story
NO MORE ALL CAPS and other pleasures of Visual Studio 14
Unpicking a packed preview that breaks down ASP.NET
Cheer up, Nokia fans. It can start making mobes again in 18 months
The real winner of the Nokia sale is *drumroll* ... Nokia
Mozilla fixes CRITICAL security holes in Firefox, urges v31 upgrade
Misc memory hazards 'could be exploited' - and guess what, one's a Javascript vuln
Put down that Oracle database patch: It could cost $23,000 per CPU
On-by-default INMEMORY tech a boon for developers ... as long as they can afford it
Google shows off new Chrome OS look
Athena springs full-grown from Chromium project's head
Apple: We'll unleash OS X Yosemite beta on the MASSES on 24 July
Starting today, regular fanbois will be guinea pigs, it tells Reg
HIDDEN packet sniffer spy tech in MILLIONS of iPhones, iPads – expert
Don't panic though – Apple's backdoor is not wide open to all, guru tells us
prev story

Whitepapers

Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Seven Steps to Software Security
Seven practical steps you can begin to take today to secure your applications and prevent the damages a successful cyber-attack can cause.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.