 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) Neither. To get IE, you had to buy the Plus! pack. (MS's bang, not mine.) (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)
|
|
(...) LOL! Alpha 1 of MSIE 3.0 didn't even come out until March 1996.[1] MSIE 3.0 was released August 1996. My MSIE 3.02 executable is dated June 4, 1997. (...) Tail end of 1997, yes. (...) March 1999. (...) No, my beef still is having to be aware (...) (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)
|
|
(...) Correction! Fixed in MSIE5! (Yay!) (...) Hmm, yet MSIE *did* change this behavior at some point between MSIE3 and MSIE5 (which is a good thing, IMHO, even if it breaks compatibility with previous versions, because it creates fewer new problems (...) (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)
|
|
"Todd Lehman" <lehman@javanet.com> wrote in message news:FrqMLK.LCo@lugnet.com... [snip] (...) probably (...) rather (...) goes (...) experience, (...) The problem with that is "arguably broken" is subjective. If one vendor thinks the standard is (...) (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)
|
|
(...) I'm saying: IMHO, it is unfortunate that Microsoft did not do what Netscape did in that case, which was to violate the spec as Netscape did. The spec ended up changing in 4.0 anyway, so if MS has done what NN did, then at least the top 2 (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|