totalxsive
Member
Please do not submit cjb.net URLs - these are vanity URLs. You should have submitted http://www.geocities.com/rubberh0e/ instead.
And yes, please provide a clickable link to the category you submitted to.
[Posted at the same to as ollie1a <img src="/images/icons/smile.gif" alt="" />]
And yes, please provide a clickable link to the category you submitted to.
[Posted at the same to as ollie1a <img src="/images/icons/smile.gif" alt="" />]
The site seems to work with IE (only?), but not with Netscape or Mozilla.
totalxsive
Member
I was able to get it to work (eventually) with Mozilla 1.1.
If a CSS file linked to from a page is unavailable, Netscape (4, on the Mac at least) will spit up a 404 error even though the main file is on the server properly.
Sucks :/
Sucks :/
I'm with Netscape 4 on this one. To my mind it's conceptually no different from a frame -- you need the file to display the page, the file isn't there -- man, you got a broken page. And, frankly, as a webmaster I'd want to know ten minutes before immediately, if the page I uploaded is broken.
I know that there are a lot of webmasters out there who really don't "know" html in any grammatical sense, who sort of schlep stuff together -- just like they were hacking a brochure in MS-Word -- and who really can't understand computer-generated errors, let alone figure out how to fix them. And the browsers don't want to be in the business of reporting errors, or of being seen as being too "picky" about common ones, so they try to do "something sensible" with them.
And you know what we get? A world in which every bleeding page has to be tested with every version of every common browser, because each one of them does something different -- sensible or accidental -- with this grammatically-incoherent stuff that should have been strangled before birth.
So a browser that immediately chokes on anything the least bit out-of-line with the most restrictive standard possible is ... what I most want (and really don't have) for all my own development work.
I know that there are a lot of webmasters out there who really don't "know" html in any grammatical sense, who sort of schlep stuff together -- just like they were hacking a brochure in MS-Word -- and who really can't understand computer-generated errors, let alone figure out how to fix them. And the browsers don't want to be in the business of reporting errors, or of being seen as being too "picky" about common ones, so they try to do "something sensible" with them.
And you know what we get? A world in which every bleeding page has to be tested with every version of every common browser, because each one of them does something different -- sensible or accidental -- with this grammatically-incoherent stuff that should have been strangled before birth.
So a browser that immediately chokes on anything the least bit out-of-line with the most restrictive standard possible is ... what I most want (and really don't have) for all my own development work.