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 let it run in normal framed mode....That's what I do to test
my Tapestry 4.1.2 based apps with selenium.
On 7/3/07, Geoff Callender <[EMAIL PROTECTED]> wrote:
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 look into whether the error
"dialog" in T4.1.2 does something similar with to what's described in
the ticket, ie. does it call dojo.html.getDocumentWindow()? I think
the Selenium TestRunner URL counts as a cross-domain URL, eg:
chrome://selenium-ide/content/selenium/TestRunner.html?test=file:///
jumpstart-max-1.5.0/web/src/test/SmokeTestSuite.html&baseURL=http://
localhost:8080
Regards,
Geoff
On 03/07/2007, at 2:25 PM, Jesse Kuhnert wrote:
> 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 than that I have absolutely no idea. I'm not sure if even a
> mozilla
> dev could tell you what was wrong with that much information.
>
> On 7/2/07, Geoff Callender <[EMAIL PROTECTED]>
> wrote:
>>
>> Hi,
>>
>> My Selenium tests that worked with T4.1.1 now fail with T4.1.2. They
>> still work just fine with Selenium IDE but not in Selenium TestRunner
>> which runs the whole suite in an IFRAME.
>>
>> It looks like client-side validation, which used to work, is now dead
>> in TestRunner. Could this be the cause...
>>
>> [Exception... "'Permission denied to get property
>> HTMLDocument._parentWindow' when calling method:
>> [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e
>> (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]
>>
>> Firebug shows that error whenever you arrive in a page with a form.
>>
>> I found a similar report but no solution: http://forums.openqa.org/
>> thread.jspa?threadID=4638&tstart=111
>>
>> Suggestions, anyone?
>>
>> Regards,
>>
>> Geoff
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
