RE: Strange Netscape Problem
by Rob Prentice <RJP(at)clickdms.com>
|
| Date: |
Mon, 30 Oct 2000 11:40:17 -0000 |
| To: |
hwg-techniques(at)hwg.org |
| |
todo: View
Thread,
Original
|
|
but IE isnt 100% w3c complient either. i think its tables that niether
display properly.
-----Original Message-----
From: Mark Stradling [mailto:mark.stradling(at)blueberry.net]
Sent: 30 October 2000 10:18
To: 'St=E9phane Bergeron'; hwg-techniques(at)hwg.org
Subject: RE: Strange Netscape Problem
> That would be nice if it really worked that way but NN 4 has=20
> so many bugs=20
> that it does break on perfectly valid code. The thing is,=20
> one should be=20
> able to code to the standards and not to any specific browser=20
> and it's=20
> usually NN 4 that has problems with standards compliant code.=20
> It's true=20
> that IE is more forgiving of sloppy code but at least it will=20
> also display=20
> compliant code perfectly... more than I can say for Netscape=20
> 4. I don't=20
> think I need to specify all the major bugs NN 4 has with CSS=20
> or the joke=20
> that is the NN 4 DOM or the fact that even its proprietary=20
> LAYER and ILAYER=20
> tags implementation is bug ridden. That's all been discussed=20
> to death on=20
> this list before. That's in addition to all the annoying=20
> display quirks=20
> that NN 4 has like the way it displays background images in=20
> table cells or=20
> the fact that it will break an image that's been sliced up in a table =
> because it doesn't disregard carriage returns in code and does so in=20
> blatant disregard with the HTML specs. I could go on and on.
Humm, 1) Give N4 a break - it's got code in it which dates back to the
student project known as Mosaic. This was build before anyone had even
thought of having a DOM! and the reason Netscape gave up on the idea of
trying to squeeze a N5 out of the same code and started the Mozilla/N6
project. N6 will be a completely new browser, with 0% inherated code
and
full standards compliance.
2) How can you complain about N4 failing on standards compliant pages
and in
the same breath complain about it NOT ignoring carriage returns in =
code.
Geez this IS what the standards say it should be doing!!! You can't
have
your cake AND eat it my friend. (An HTML browser should reduce all
white
space, spaces, tabs, line breaks, carriage returns, etc into the =
single,
non-breaking white space character, Chr 160.
Anyway, all of this is irrelivent. It doesn't matter that Netscape 4
isn't
standards compliant, nor that it has some accepter bugs. what matters
is
that around 25% of the Internet population use it as their only or main
browser.
If you want me to use your site, buy your product/service you WILL make
your
site work on the browser I choose to use or I will simply go else =
where.
Remember, your competitor (or your client's competitor) is only a mouse
click away.
Regards,
Mark Stradling
HWG hwg-techniques mailing list archives,
maintained by Webmasters @ IWA
This page is part of a preserved archive of archives.hwg.org. The site is no longer active and its content is not maintained. For enquiries about this archive, write to archive(at)iwanet.org.