 | | Re: Why MSIE sucks for the HTML writer —Scott Smallbeck
|
| | | (...) Just tried that on IE5 and the searches worked fine. Entered the value and pressed enter. _ _ Scott Smallbeck scotts@contactics.com (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | |
| | | | | Re: Why MSIE sucks for the HTML writer —Todd Lehman
|
| | | | (...) Thank gawd. Finally. --Todd (25 years ago, 17-Mar-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Why MSIE sucks for the HTML writer —Mike Stanley
|
| | | | (...) So are we going to see an announcement that people need not worry about bugging "their browser vendor" because of some problem that IE had 2 versions ago? :) (25 years ago, 18-Mar-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: Why MSIE sucks for the HTML writer —Todd Lehman
|
| | | | (...) 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 (...) (25 years ago, 18-Mar-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Why 3-year old mayonase tastes bad —Asher Kobin
|
| | | | (...) 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 (25 years ago, 20-Mar-00, to lugnet.admin.general)
|
| | | | |
