> The "very bad position" I'm referring to is not technical, but more
> marketing. The "word is getting out" that Netscape6 does not handle
> certain things, so developers need to exclude it.
These would be the same developers who use Flash to exclude the blind, and
frames and compulsory Javascript to exclude Lynx users?
Do they really think that, by not coding for Gecko, people are going to
stop producing browsers which use it?
> I've gotten code
> from third parties sent to me that they want to include on our site
> and it specifically excludes Netscape6 because they say it doesn't
> work.
It doesn't work? The two-facedness of the web developer community is
amazing. "Standards!" they cry. "We only want to write stuff once!" they
cry. We give them standards, and then they moan that their non-standard
stuff doesn't work any more.
You can write a standards-compliant code path that works in Netscape 6 and
IE 5. There's all sorts of migration guides (Eric Krock's, for one.)
I can soapbox for ages, but it won't achieve much... The point is made.
Gerv
