|Disabling add-ins to speed up browsing||
If Internet Explorer 9 displays the message: Speeding up browsing by disabling add-ons, choose Don't disable or select a bigger threshold value.
Creating and running steps that start an InPrivate Browsing session is supported only by using Tools > InPrivate Browsing.
Using toolbars or extensions for this operation may cause Microsoft Internet Explorer to behave unexpectedly.
Creating and running steps that are related to tabs, such as selecting a tab or creating a new tab is not supported when Microsoft Internet Explorer is in Full Screen mode.
Workaround: Add a <Browser>.FullScreen step before and after the desired step to toggle Full Screen mode.
Test Objects, methods, and properties
Recognition of test objects when using AutoXPath is very slow for web pages in Quirks Mode and Almost Standards Mode.
Convert the web page into Standards Mode by doing one of the following:
|RunScript / RunScriptFromFile methods||
When using the RunScript or RunScriptFromFile methods, Alert, Confirm, or Prompt dialogs are not displayed.
Workaround: When writing a RunScript method, use the following method syntax:
|WebXML test object||
The WebXML test object is not supported on Internet Explorer 9 or later running in standard mode.
Accordingly, features related to WebXML test objects, such as XML checkpoints and output value steps, are not supported on such browsers.
In some cases, UFT does not support or recognize about:blank tabs in Internet Explorer 11.
|Early versions of Internet Explorer||
When using Internet Explorer 9, the innertext, outertext, innerhtml and outerhtml property values may differ from earlier versions of Internet Explorer.
Therefore, using these values in parameters or running checkpoints that use these property values may cause the steps to fail.
When recording a test on Internet Explorer 8 or earlier with the Active Screen enabled, performance on the site may become very slow.
Workaround: Record the test using Internet Explorer 9, or disable the Active Screen.
For details, see the Unified Functional Testing User Guide.
Drop-down boxes in a web page
UFT may respond slowly during a recording session if the drop-down boxes in a Web page contain a lot of data.
Workaround: Learn the objects on a Web page that contains a lot of data (instead of recording).
Recording on an Oracle ADF object in Internet Explorer may result in performance issues.
|Items not recorded||
Switching between internet and intranet sites
UFT does not record steps when switching between an Internet site and an Intranet site, if you are using Internet Explorer with:
Workaround: Set the integrity level (Protected mode enabled or not enabled) to be the same for the Internet and Intranet zones.
Customized toolbar buttons
UFT records only on the toolbar buttons displayed by default in Internet Explorer, and does not record on customized toolbar buttons.
UFT does not record on the Find window of the Microsoft Internet Explorer browser.
In Internet Explorer, the AutoComplete operation on edit fields is not recorded.
Workaround: You can disable the AutoComplete feature in Microsoft Internet Explorer by selecting Tools > Internet Options > Advanced and deselecting the Use inline AutoComplete under the Browsing options in Microsoft Internet Explorer.
Specific SAP objects and methods
Recording the following methods in Internet Explorer may have unexpected results:
Workaround: If your script is not recorded correctly, do one of the following:
If you record a click on an area of an image map that is not mapped to a URL in Microsoft Internet Explorer, UFT will perform a click on the first mapped area of that map during the run session.
When recording on an combo box object in which the role property is "listbox" (and is recorded as a WebList object), UFT adds additional WebEdit.Set steps to the test when you select a value from the object with the .Select method.
Workaround: Delete the unneeded WebEdit.Set steps.
Recording on web pages built in Angular is not supported in Internet Explorer.
When using Internet Explorer versions 10 or 11, if you use the Active Screen to view objects or add steps to a test or component, the Active Screen does not capture the updated state of the Web page.
Workaround: Open the Developer Tools for the Web page and change the Document Mode to 8 or lower.