FF problem recognizing specific iFrames

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 21 Jan 2015 13:57 by ADMIN

ADMIN

Ivaylo

Created on: 06 Nov 2014 09:20

Type: Feature Request

FF problem recognizing specific iFrames

Record against the following page with Chrome JS Recorder or IE and run with FF 33: it fails with the following error:

http://it-help.bathspa.ac.uk/iframe_demo.html

Error on execution is:

Unable to find the target host (Browser/SilverlightApp) to locate an element. Failure: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null
BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'26f68721-5335-46f2-98c6-c83925351d5f',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'0',InError:'True',Response:'mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null')
InnerException: none.

   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.RefreshDomTree()
   at ArtOfTest.WebAii.Core.FramesCollection.EnsureDomLoaded(Browser browser)
   at ArtOfTest.WebAii.Core.FramesCollection.get_Item(FrameInfo frameInfo)
   at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.GetFrameBrowserInstance(Browser topBrowser, FrameInfo frame, Int32 waitTimeout, String& stringError)
Unable to find the target host (Browser/SilverlightApp) to locate an element. Failure: ArtOfTest.WebAii.Exceptions.ExecuteCommandException: ExecuteCommand failed!
InError set by the client. Client Error:
mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null
BrowserCommand (Type:'Information',Info:'DocumentMarkup',Action:'NotSet',Target:'null',Data:'',ClientId:'26f68721-5335-46f2-98c6-c83925351d5f',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'0',InError:'True',Response:'mozCommandProcessor: GetCurrentDocumentMarkup(): Exception thrown while trying to serialize the Dom. Error: TypeError: this.TargetDocument is null')
InnerException: none.

   at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.RefreshDomTree()
   at ArtOfTest.WebAii.Core.FramesCollection.EnsureDomLoaded(Browser browser)
   at ArtOfTest.WebAii.Core.FramesCollection.get_Item(FrameInfo frameInfo)
   at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.GetFrameBrowserInstance(Browser topBrowser, FrameInfo frame, Int32 waitTimeout, String& stringError)

3 comments

ADMIN

Daniel Djambov

Posted on: 21 Jan 2015 13:56

Telerik: Unfortunately there is a new security restriction in new versions of Firefox, which is not allowing us to see the DOM tree of the cross-domain frames. The other browsers have the same restriction, but unlike Firefox they also provide a way for automation tools to work around this. For example, IE has a setting which we have access to via our browser calibration and Chrome has a command line switch allowing us to start it in proper for testing mode. It is out of our control for the time being and until Firefox releases a version with solution, we cannot workaround it.

ADMIN

Iliyan Panchev

Posted on: 15 Jan 2015 06:48

Hi, we are currently working on the issue. Will update you when there is a fix for the problem. 
Thank you for your patience and understanding!

John

Posted on: 15 Jan 2015 00:26

Using Telerik Test Studio v 2014.4.1211.0

I was able to record UI activity within an IFrame normally with Chrome and IE (the elements populated in my element library).

The same activity would not record in FF (nothing inside the IFrame populated within Telerik's DOM utility).

Tests fail at IFrame steps in FF v. 34.0.5, same errors as above. I added a RefreshDOMTree() to no avail.