Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do you make your website CSS3 compatible with Internet Explorer versions earlier than IE9 without using plugins such as CSS3pie, normalize, etc?
CSS3Pie is a great tool I was using, but it became inconvenient because I have some elements with border-left-radius that do not work with the plugin.
IE8 doesn’t support CSS3. You know that already. If you’re looking for a way to get CSS rounded corners in IE8 without some kind of hack, then you’re going to be disappointed.
Solutions:
Use “Progressive Enhancement” techniques, such as CSS3Pie, which you already know about. Virtually all of these are Javascript-based hacks, and none of them are perfect. You already know the issues with CSS3Pie. The issue you discuss is a relatively minor one, and easily worked around; if you’re not willing to work around that, then there’s unlikely to be anything better for you.
A fairly comprehensive list of these polyfills can be found here: https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills
Graceful degradation. This basically means accepting that old browsers are missing some features, and writing your site so that if those features are missing, then it still works; maybe not as good, but usable. In the case of
border-radius, this is easy: just accept that it doesn’t work in IE8. Rounded corners are nice to have, but the site isn’t going to be broken beyond use without them.Chrome Frame. This is a plugin for IE written by Google that allows it to render pages using the same rendering engine as the Chrome browser. It’s a major hack to the guts of the browser, but it does work well; no more worry about those missing features and rendering glitches. However, it requires the end user to install the plugin, so while it’s nice as an option, and you can specify it to be used if it’s available, you can only really rely on it if you have control over the end users’ systems – eg in a corporate network where you can make sure it’s installed on all machines.
Those are your options.