I've been doing some Opera5 testing, and actually got a few things working.

Currently it seems Opera doesn't support dynamic loading (major problem) I
posted a bug to Opera about this.. so hopefully it will get fixed.

So the rest of my tests were done using normal <script> linking.
Everything links in perfectly and loads in correctly.. The default
DynAPI.document gets created correctly (after a minor fix.. already in CVS
Doug ;)

Now I ran into a real problem, can't solve it as of yet.. Posted about it to
the opera-users list.. but I think that's the wrong list (nobody seems to
have a clue, and they are mainly discussing problems with unsubscribing from
that list ..duh :)

here's the code that starts the errors:

in DynLAyer.createElement, the part that creates the parentElement won't
work:

                var
parentElement=(this.parent.isDynLayer)?this.parent.elm:this.parent.doc.body;

Problem is, it seems that Opera's HTMLDocument object contains all standard
DOM objects.. except the body object (the only one we actually use). Again I
posted a bug about this, and a question to the Opera list, but my best hope
is people on this list.

Maybe I'm missing something? Is there another way to create the DIV tags in
the correct document.
note that this does work:

                var
parentElement=(this.parent.isDynLayer)?this.parent.elm:this.parent.doc;

it will return a valid HTMLDocument object, but as mentioned, without the
.body object property, which is the object we need to create divs in.


if anyone can solve this, PLEASE DO, and let me know (and to take Jordi's
idea of coding, I'm making this my personal war :) Opera seems to be a VERY
fast browser, and delivers all that Mozilla promissed, so it's very well
worth the support of webdesigners. (and it's only 2mb without Java!)


Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to