 | | DYA announcements in lugnet.shopping
|
|
I am wondering about the clutter that is occuring in lugnet.shopping from the many DYA posts. I really get a lot of value from lugnet.shopping (Just bought a couple of sets from NoodleKidoodle.com) but it was quite a chore sorting through the (...) (27 years ago, 21-Mar-00, to lugnet.admin.general)
|
| |
 | | 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)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) Probably the same thing that would happen if MSIE had a 100% market share. (In lugnet.admin.general 5378, Asher Kobin wrote: (...) ) eric (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)
|
|
"Asher Kobin" <asherk@pobox.com> wrote in message news:FrqHo3.2KJ@lugnet.com... (...) MacOS9... (...) with the (...) the (...) item at (...) to (...) How come I can't get IE5 to reproduce this on my machine? Here is the page I was using to test it. (...) (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, just so I understand this, you're saying that MS, a company that is almost universally condemned for _not_ adhering to standards, should have done what others (and maybe you) have screamed about all along - that is violate those standards? (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) I was actually interested to see what it was... And in fact I do understand competition, but I also understand standards. If you want people to use your browser, you should make it faster, or use less memory, or have more _client_side_ (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) Are you ignorant? Do you understant competition? What would happen If every car was the same? We want people to use our browser, so obviously we have to make it better (what the Linux world calls embrace and extend). We are more RFC compliant (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Re: Why MSIE sucks for the HTML writer
|
|
(...) For Linux users, Microsoft recommends following the instructions in this KB article: (URL) I can't answer your question, but I can say that Microsoft's awareness (and interest) of the Linux OS has increased dramatically, although it did take (...) (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 have a web page on www.lugnet.com which sends out four multiple-select lists. In each of those lists, I want _none_ of the list items to be pre-selected. If the user clicks Submit without explicitly selecting any items in any of those list (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | 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)
|
| |
 | | Re: MSIE5 better but still buggy (was: Re: Why MSIE sucks for the HTML writer)
|
|
(...) This is referring to the "many-from-many" (a.k.a. "MULTIPLE") version of <SELECT>, BTW, not to the "one-from-many" version of <SELECT>. --Todd (27 years ago, 20-Mar-00, to lugnet.admin.general)
|
| |
 | | Why 3-year old mayonase tastes bad
|
|
(...) and (...) How do you define "recent"? Do you consider Nav4.0 recent? If so, then people who are running "recent" versions of nav are open to some pretty scary security holes. (...) You're really streching it here... Subject says it all (27 years ago, 20-Mar-00, to lugnet.admin.general)
|