Known Issues - Web 2.0 Add-ins
This section contains troubleshooting and limitation information about working with the Web 2.0 Add-ins.
When working with test objects that are supported using Web Add-in Extensibility, such as Web 2.0 test objects, if you create a checkpoint from the Active Screen, or try to view the object's properties from the Active Screen, some property values may be empty.
When working with Web 2.0 toolkits on Firefox browsers, we recommend loading only one toolkit at a time.
Due to synchronization issues, if you navigate to a new Web page in Internet Explorer or Mozilla Firefox while recording, then UFT may not record certain operations on certain ASP .NET Ajax or jQuery UI objects in the page. Similarly, when running steps that navigate to a new page, UFT may fail to perform certain steps on certain ASP .NET Ajax or jQuery UI objects.
Workaround: If the problem occurs while recording, refresh the Web page and record the step again. If the problem occurs while running, insert a Wait() statement before the problematic step.
Web 2.0 test objects or Web Add-in Extensibility-based test objects are not supported on Safari browsers.
When working with the Web 2.0 ASPAjax Add-in, running scripts in the Active Screen is not enabled by default.
In the Options dialog box, enable running scripts in the Active Screen. In Tools > Options > GUI Testing tab > Active Screen node, set Run scripts to Enabled.
Close and reopen your test or component for the setting to take effect.
You cannot not record on objects created with Dojo 1.10 in Internet Explorer 10 or 11.
Workaround: Record the objects on Internet Explorer 9, Firefox, or Chrome.
When loading the Ext-JS toolkit, ensure that the Siebel Add-in is not loaded.
When recording in a jQueryUI application on the Chrome emulator if you open new tab (for example, by a click operation on an object) and then record actions on the new tab and close the tab, actions performed on the original tab are not recorded.
Workaround: In Chrome, do the following:
Navigate to the chrome://flags/ page.
In the /flags page, set the Enable touch events option to enabled.
By default, all SiebelOpenUI objects appear as child objects of the same Page object, even for objects embedded in objects that are opened from the main page.
If you need to group objects under separate Page objects, select the Every navigation option under the Create a new page test object for section in the Page/Frame Options pane of the Options Dialog box (Tools > Options > GUI Testing tab > Web pane > Page/Frame Options).
When recording entering information for a SblOUIAdvancedEdit object, UFT records the Set method for the entered information after the opening of another object.
Workaround: Manually change the order of the steps after recording.
When selecting a method for Siebel OpenUI objects, the autocompletion list displays some of the object's internal methods. These methods should not be used in your test.