 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) for the love of god, please no! Ideally there would be 10s of browsers available, but they would all render the same pages in the same way. I have never used IE, and have no plans to - especially since there's no version for my OS of choice. (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: MSIE5 better but still buggy (was: Re: Why MSIE sucks for the HTML writer)
|
|
(...) Ok, well I couldn't stop from smiling when I read your post. It sounds to me that Netscape did a little "embracing and extending" of its own in this area :) (...) I don't understand your question... (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) I'd like to see that browser be Mozilla, but MSIE is still far, far more solid. BTW, does MS have any plans to release a Linux version of MSIE? Or is it recommended to run it under WINE instead? (...) This thread has helped a lot. I actually (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) fixing (...) Backward compat is a sometimes difficult issue to deal with. Case in point, because of the many differences in the rendering capabilities between Nav and IE, many site authors have to write small workarounds to get even polarity (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: MSIE5 better but still buggy (was: Re: Why MSIE sucks for the HTML writer)
|
|
(...) Well, maybe you're right about that after all. According to section 8.1.3 of RFC1866[1] (HTML 2.0), "[t]he initial state has the first option selected, unless a SELECTED attribute is present on any of the <OPTION> elements." (This is (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|