 | | 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)
|
| |
 | | Re: MSIE5 better but still buggy (was: Re: Why MSIE sucks for the HTML writer)
|
|
(...) It selected an item in the list which didn't have the "SELECTED" attribute. That's broken, period. (...) aha. --Todd (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)
|
|
(...) Why do you consider this difference in behavior between the two browsers to be "broken" in IE5? Obviously, I can make the reverse argument and say it is "broken" in Nav. Neither browser is going to change this behaviour, it will break (...) (27 years ago, 20-Mar-00, to lugnet.admin.general)
|