Re: Script error on Google Homepage

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Roland Hall wrote:
>> Now you're being silly. Netscape 6 is Gecko-based. There is nothing
>> about Netscape's innerHTML support that reflects backward
>> compatibility because None of the pre-Gecko Netscape browsers had
>> such support.
>
> I'm talking about non-standard support in FF half ass
> supporting innerHTML with a strict document type and
> you're whining something about NS6 like it's a current
> browser.

No.

I am drawing a distinction between backward-compatibility and new
compatibility. If Netscape had not abandoned backward-compatibility in the
Mozilla project, there would be three competing DOMs today: those of the
W3C, Netscape, and IE. [innerHTML] was part of the IE DOM, not Netscape's,
and therefore cannot be considered "backward-compatibility" for Gecko-based
browsers[1].

Maybe you haven't been around long enough to remember
document.layers["a"].document.layers["b"].document.forms[0].elements[2]
references, but that doesn't mean they never existed.

Your problems achieving Firefox compatibility are /*NOTHING*/ compared to
what we all went through when there were completely divergent DOMs. And the
desire to NEVER GO THERE AGAIN is what makes so many of us embrace
standards-based development.



> It's not.

I did not claim Netscape 6 was a current browser. I said it was Gecko-based.



> It supported innerHTML and FF supports it half ass.

Are you claiming that Netscape 6 supported innerHTML more completely than
Firefox does? And what do you mean by "half ass"? Could you please point us
to the document that specifies how innerHTML support should look?



> I believe NS6 came out before Firefox, did it not, but let's
> stay on topic.

You are putting words into my mouth. Recall:

>>>>>>>> Netscape realized it had to design a browser with
>>>>>>>> conformance and that this neccessarily meant
>>>>>>>> abandoning backward-compatibility.

The Mozilla Project[2] spawned the standards-based Gecko engine. Since v6,
all versions of Netscape have used the Gecko engine. Every version of the
Mozilla browser has used the Gecko engine. Every version of Firefox has used
the Gecko engine. See the point? THEY ALL HAVE THE SAME DOM.



> If the browser supports anything non-standard with a
> strict doctype, it's not 100% standards compliant.

That is 100% wrong[3]. Conformance is browser measured against the standard,
not standard measured against the browser.




[1] Unless you take it to mean "compatibility with code written by backward
developers"
[2] Please do not trip on the word Mozilla here - in 1998, "Mozilla Project"
was synonymous with "next-generation Netscape browser". It is now under the
umbrella of the non-profit Mozilla Foundation
(http://www.mozilla.org/foundation/)
[3] And it would be fun to watch you apply that assertion WRT DOM Level 0.

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.


.

Relevant Pages

  • Re: VMS V8.3 (et al.) v. Netscape Navigator Gold Version 3.03
    ... I still use the old Netscape ... browser on my main Alpha system, ... Or am I the last Netscape 3 user left on VMS, ... (Netscape's beyond support, I ...
    (comp.os.vms)
  • Re: innerHTML vs. replaceChild()
    ... If the browser doesn't support innerHTML, you will get an error on ... in my case I'll just avoid .innerHTML for HEAD ... I see no reason in the thread you quoted why my function below ...
    (comp.lang.javascript)
  • Re: innerHTML vs. replaceChild()
    ... If the browser doesn't support innerHTML, you will get an error on ... it just omits some functionality. ... But I'll want to support non-W3C DOM browser for a while yet. ...
    (comp.lang.javascript)
  • Re: innerHTML vs. replaceChild()
    ... If the browser doesn't support innerHTML, you will get an error on ... Therefore, if `innerHTML' is not supported, the reference evaluates ... Yet I wonder if such a user agent even exists or could exist successfully ...
    (comp.lang.javascript)
  • Re: OT Ebay does not like netscape
    ... we recommend upgrading your Web browser. ... include the use of the latest security updates and support of interactive Web features. ... what version of netscape are you using? ...
    (rec.collecting.coins)