We value your privacy.
We use cookies to enhance your browsing experience, analyse site traffic, and personalise content.
By clicking “Accept all”, you consent to our use of cookies. You can also choose
“Essential only” or learn more.
>In general, it is a bad practice to write a page to be specific to one browser. In my case, if I run into a site that is IE specific, I cross it off my list and never go back. The same would be true if it were specific to any browser. Anyone that writes a site specifically for IE is a fool. There is no need to do that as most of them that I have seen look the same in other browsers if you remove the items specific to IE. I managed an oem software group for a few years. We were writing in ANSII C. Most all of the compilers have extensions that allow some things to be done a bit differently and perhaps speed things up or make it a bit easier. We NEVER used those. There is always a chance that we would change micros and/or compilers. If we used the extensions, we would have to rewrite much of the code. If we followed the standards, it was mainly just a recompile.
The usage of other browsers is getting more common. A good portion of the front runners and tech savvy use other browsers. If you want to get to this audience, IE specific is not the way to go. One interesting thing to me is that the box model (which I mentioned earlier that IE does not support) gives you much more control over the look and feel of the page, beyond anything that IE adds to the party.