 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) Once a bug, always a bug. That's the way it is serving HTML, until an old release trickles off to zero. MSIE3 is still buggy and still in use. I titled the subject "Why MSIE sucks for the HTML *writer*" not "Why MSIE sucks for the user". (...) (...) (27 years ago, 18-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) What is supposed to be broken about it? It looks ok in my MSIE 4. Frank (27 years ago, 18-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) And it's even green! (Temporarily ;-) -Shiri (27 years ago, 18-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) No. If it's fixed finally in MSIE, then it's not an issue for MSIE users with recent browsers. If someone is running a browser which has the same bug that MSIE3 had, and it isn't fixed in the current release, and they can't get the source code (...) (27 years ago, 18-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) It's a HUGE deal. You leave a search button off a form by accident (on a page with more than one form) and some poor user out there is up the creek without a paddle, and probably doesn't know why, or can't switch browsers. :-( (...) IMHO, it (...) (27 years ago, 18-Mar-00, to lugnet.admin.general)
|