Knowledge Base Article

Home Page > Knowledge Base > Rapise

Home Page > Knowledge Base > Rapise > Rapise Web

Article What to do When Rapise Doesn't Display the Web Page DOM?

by Adam S on Friday, September 2, 2016

Sometimes when testing certain web applications instead of the browser DOM tree appearing you will see strange results such as "Node0" appearing. This is caused by the application using nested frames with potentially different security origins. This article describes some of the common issues and describes the solution.

Example - Gmail

A good example of this issue can be found when using Rapise to test Gmail. If you open up Gmail and go to the Inbox you will see:

If you then try and inspect this page using certain browsers, you will see the following:

Instead of seeing the browser DOM tree you see 'Node0' as the only item. This is an indication that you need to change the browser profile.

Configuring Chrome

In our example, Chrome is restricted from displaying the child IFRAME elements due to their security settings:

The solution is to open up the browser profile manager in Rapise:

We recommend clicking 'Duplicate' to create a new cloned browser profile which we'll call "Chrome X-Frame HTML":

You can keep the same settings as the default "Chrome HTML" profile with the addition of the following items to the "CMD Line Parameters" setting:

     
  • CMD Line Parameters = --disable-web-security --user-data-dir="<Path to Your User Data Folder>"

For example, we used this:

     
  • CMD Line Parameters = --disable-web-security --user-data-dir="C:\Users\fred.bloggs\AppData\Local\Google\Chrome\User Data"

Once you have created this profile, switch Rapise to use this profile in the "Start Page" and then try using the Web Spy again:

 

Now you will see the DOM Tree correctly loaded.

Configuring Firefox

In our example, Firefox is restricted from displaying the child IFRAME elements due to their security settings:

The solution is to go to the about:config special URL:

Then change the setting:

security.fileuri.strict_origin_policy -> false


Once you have changed this setting in Firefox, try using the Web Spy again and you will see the DOM Tree correctly loaded.

Configuring Internet Explorer

With IE there is nothing special that needs to be done, it will be able to display the DOM window normally. However on some PCs IE is very slow as a web browser and the DOM tree may timeout, so contact support if you experience that issue.


Attachments
Article Info
Last Updated: 9/2/2016
Article ID: KB219
# Views: 68
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.