Thanks Jesse. Your suggestion fixed it. I'd lost sight of the fact
that the "chrome" proxy was experimental and that there's always the
original way of using TestRunner.
Chrome is great because it is non-invasive (ie. you don't have to
alter your web server and/or wars/ears to use it), bu
That patch is for PopupContainer - which isn't part of the simple
AlertDialog mixin that Tapestry does with the dojo Dialog object. (well it
is part of the object, but not something Tapestry duplicated)
Alternately, you could just not use the experimental proxy injected feature
of selenium and le
Jesse,
Thanks, but I'm sad to say that there are no other error messages to
go on.
However, dojo was patched in April for an almost identical problem:
http://trac.dojotoolkit.org/ticket/2723 - PopupContainer load
error within a cross-domain IFRAME
Would you be able to have a quick loo
That's an internal error thrown by the mozilla dom implementation.
nsiDOMEventListener is the class and handleEvent is the method
NS_ERROR_XPC.blahblah is just some constant and the hex-y looking string
is probably the current op code in the current pseudo js vm context...(i
think?)
Other tha
