not sure if this started about the same thing, but I introduced an is.def
property before. This was because alot of code is used in NS6 AND IE5 ..
using an is.def property for those if loops, would give minor speed
increases to those loops for the default browsers (that's what the .def
stands for :)
so maybe we should remove the is.def property and treat the is.dom in
that way.. use it for general code loops that work on NS6 AND IE5 for now..
testing for true DOM support is just not worth it and probably not possible
seeing the current line up of DOM implementations.
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Cameron Hart
> Verzonden: dinsdag 13 maart 2001 19:17
> Aan: [EMAIL PROTECTED]
> Onderwerp: RE: [Dynapi-Dev] DynAPI X
>
>
> > >so unfortunately I can't test my theory ;-)
>
> > I did test it and the problem is that ie 5 mac supports stuff
> > like createElement but it still buggy when you go many level
> > deep or when you start adding html to layers there are a lot of
> > timing issue with ie 5 mac
> > I would live ie 5 mac code like ie 4 code it seems to work better
>
> That's the trouble with theory. Nevermind.
>
> Well perhaps I should change the is.dom condition back, although
> frankly we
> may as well make it is.dom=is.ns6 because that's effectively what it was
> doing.
>
> Or I could try making the test stricter. What do you developers expect
> something that passes the is.dom test to be able to do?
>
>
> _______________________________________________
> 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
