> According to > http://sites.netscape.net/ekrockhome/standards.html , there > are certain guidelines to follow in order to be W3C compliant. Looking > through the code of dynlayer.js, for example, 'document.all' > and 'document.layers[]' > will not be recognized by NS6 and future browsers endorsing > the open standards. > i think it is essential to build DynaAPI 2 on the solid > foundation of W3C DOM > in order to be future proof. Don't have the DynAPI2 code here, but can't see (in other code) where document.all or document.layers is used. Again, we could make DynAPI2 W3C Dom compliant, but making sure NS6 works is more important. I know, NS6 is DOM compliant.. if it's fully DOM compliant, other dom browsers will also work with the same tricks and updating will be easy, but I'd rather make sure NS6 is supported then making sure a written standard is supported (but browsers can still cause problems) > Yes, NS6 is the culprit here. But I would need my code to work on all > versions of the browser. Use other code then, your code doesn't seem to be working on NS6, so either your code is wrong or NS6 seems to have a bug and you have to work around it. Again, it's not a DynAPI bug :) cya! Pascal Bestebroer ([EMAIL PROTECTED]) Software ontwikkelaar Oberon Informatiesystemen b.v. http://www.oibv.com _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-dev
