This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From email thread: Hi, folks- Lea pointed out that right now, the site looks pretty bad in IE8. I know we all want developers to use modern browsers... but something like 7-15% of our users may have to use the site in IE8. What is our legacy browser strategy? Do we only support modern browsers? Do we launch as is, and say we'll evaluate IE8 support in the future? I don't see a practical way to support IE8 before launch... Regards- -Doug Eliot Graff wrote: > Like any good web development, we should be using feature detection > and fallback code for any recently implemented features. I realize > that's considered extra work, but isn't that best practice? And should > we be employing best practices? We can think of IE8 as a canary in the > coal mine for this.
Basically, the main unresolved issue in IE8 is the logo. Everything else looks decent and works fine, on par with progressive enhancement.
Logo issues were resolved.