maybe we should hard code into the is.dom property to not include IE5/4
windows (I think IE5 windows passes the test, but it's not DOM compliant)
this way we can replace some of the is.def checks with is.dom ..
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Cameron Hart
> Verzonden: dinsdag 13 maart 2001 15:32
> Aan: [EMAIL PROTECTED]
> Onderwerp: RE: [Dynapi-Dev] DynAPI X
>
>
> I was just looking at the mouseevent code, and I've got a suggestion.
> Instead is going (is.def&&!is.ie), why don't you say is.ns6
> OR create a new
> is.dom2 test or is.dom2e (e for events). I'm think NS6 is
> probably the only
> browser that does DOM2 events at the moment anyway, but
> providing a dom2e
> test would allow future DOM2 compliant browsers to run this code.
>
> I'm figuring there are different levels of the DOM, so we
> should test for
> these and use them where appropriate. At the moment (since I
> just changed
> it), the is.dom test test's for DOM1 stuff, IE5 Mac should
> now pass this
> test (but Opera won't). There is nothing in the DOM that lets
> you ask the
> browser, "are you dom1 compliant", so I'm just testing for
> DOM stuff that is
> used by the API.
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev