Known Issues - Mozilla Firefox
General
Multiple versions of Firefox |
If two minor versions of Mozilla Firefox are installed on the same computer, and the earlier version was installed after the later version, UFT One may not recognize which is the latest version. |
Other Firefox add-ins and the Add-ons Manager |
|
User Account Control enabled |
If you are working on a computer where the UAC (User Account Control) option is set to ON, UFT One does not support testing on Mozilla Firefox browsers that were installed (or upgraded to a new version) after you installed UFT One. Workaround: After installing Mozilla Firefox on the environment described above, log in as an administrator and open UFT One. This enables UFT One to install files that are required for Mozilla Firefox support. |
Anonymous content elements |
UFT One does not support anonymous content elements in non-XUL frames. (For example, the buttons in the Mozilla Firefox SSL exception page.) |
SAP WDJ Add-in |
The SAP WDJ Add-in is not supported on Firefox browsers. |
Privileged URLs |
If you are testing on a Firefox version 57 and higher, a Firefox limitation prevents you from navigating to privileged URLs. UFT One will display an error if your test step navigates to a privileged URL in Firefox. You can then stop, skip, or edit and retry your step. For more details, see the MDN web docs. |
Enable Micro Focus UFT Agent extension installation in your browser policy |
If the extension fails to install due to your browser policy, manually add the Micro Focus UFT Agent Firefox Extension to the list of extensions to install. For details, see https://github.com/mozilla/policy-templates/blob/master/README.md#extensions. The path to add for this extension is: Caution: Make sure that your company's security policies permit you to make this change. |
Recording
Prerequisites |
Recording on Mozilla Firefox pages is only possible when the page is fully loaded. |
Unsupported methods and features while recording |
|
Troubleshooting additional steps |
When recording steps in Mozilla Firefox, additional steps may be recorded. Workaround: Manually remove the extraneous steps after the recording session ends. |
Missing Submit operations |
When recording on some Mozilla Firefox versions, if you perform a search on google.com by entering the search string and then pressing Enter, the Submit operation is not recorded. Subsequently, when you run the test, UFT One enters the search string but does not perform the search. Workaround: Do one of the following:
|
If Handler option |
The If Handler option in the Web Event Recording Configuration Dialog Box works on Mozilla Firefox browsers only if the handler is assigned as an attribute. For example, <A onclick = "some code"/>. The If Handler option does not work if the handler is assigned as a property. For example, aObj.onclick = function() {some code}. |
CloseAllTabs methods |
When recording on Firefox versions 57 and higher, steps that close the last tab of the browser, or all browser tabs in a window, are not recorded. |
Test Objects, Methods, Properties, and Checkpoints
Closing a browser window |
If a test or business component contains a step that closes a Mozilla Firefox browser, UFT One may behave unexpectedly when that step is reached during a run session. Workaround: Do not include a step that closes a Mozilla Firefox browser. |
Dragging and dropping |
|
Edit boxes |
The Object Spy and Checkpoint Properties dialog boxes do not retrieve the current value of edit boxes in Mozilla Firefox dialog boxes. |
hwnd property |
The hwnd property is not supported when working in Firefox versions 57 and higher. |
Property values and checkpoints |
When using Mozilla Firefox, the innertext, outertext, innerhtml and outerhtml property values may differ from other browsers. Therefore, using these values in parameters or running checkpoints that use these property values may cause the steps to fail. |
RunScript method |
When using the RunScript method on Mozilla Firefox browsers, you should disable the Content Security Policy before running the test:
|
Search or developer toolbars |
If you open the Search toolbar or developer toolbar in Mozilla Firefox, when you spy on an object or highlight an object in the object repository, the highlight rectangle is displayed in the wrong location in the browser window. Workaround: Float the toolbar in the browser window. |
Snapshots | If you take a snapshot of an ASPAjaxRichTextArea object on FireFox, it might not be displayed correctly in the Active screen. |
tabmodal dialogs |
The Object Spy and Navigate and Learn dialog boxes do not retrieve the current value of tabmodal dialogs in Mozilla Firefox. |
Text area checkpoints |
Text area checkpoints are not supported on Mozilla Firefox. |
Type property for WebButton test objects |
The Type property of the WebButton test object has a different default value in Microsoft Internet Explorer and Mozilla Firefox. In Microsoft Internet Explorer the default value is Button, but in Mozilla Firefox the default value is Submit. Workaround: Do not use the Type property in the description of a WebButton test object. |
Browser dialog boxes
General
Mozilla Firefox uses different standard dialog boxes than Windows standard dialog boxes used by Microsoft Internet Explorer.
Due to the difference in standard dialog boxes, pop-up recovery scenarios that use the Click button with label recovery operation and were built for Microsoft Internet Explorer will not work for Mozilla Firefox, and vice versa.
Alert, Confirm, and Prompt dialog boxes
You cannot spy on Alert, Confirm, and Prompt dialog boxes opened by the browser but you can record and run scripts on them.
If you create steps on such dialog boxes, use Browser.DialogExists, Browser.HandleDialog, and Browser.GetDialogText methods to automate the dialog box behavior. See the following example.
For dialog boxes of other types, such as Authentication, Security Alert, and Certificate dialog boxes, use UIA add-in or AI features in UFT One to handle them.
Example: The following example verifies whether a browser dialog box exists. If the dialog box does exist, it retrieves the message displayed, clicks the OK button, and closes the dialog box.
Browser("Example").Page("Buttons").WebButton("Pop up!").Click While Browser("Example").DialogExists = false wait 2 Wend txt = Browser("Example").GetDialogText If txt = "expected value" Then Browser("Example").HandleDialog micOK End If
Dialog box opened from a cross-origin frame
Mozilla Firefox version 69 or later: Dialog boxes triggered by elements inside cross-origin frames are not supported.
Note: The HandleDialog , GetDialogText, and DialogExists methods may have unexpected results in the following scenarios:
- If you manually open a dialog box outside of your run session
- If you manually close a dialog box during your run session
Unsupported test objects, methods and functionality
The following test objects, methods, and other Web-specific functionalities are not supported in Firefox:
-
about://* pages
-
Browser.Object method
-
Browser.Stop
-
Firefox Start Page
-
Frameset objects are not supported in Mozilla Firefox browsers.
- Local system monitoring is not supported in Mozilla Firefox.
-
ViewLink test object
-
Dialog test object (See Dialog object in (missing or bad snippet))
-
WebAudio.Play. Workaround: In Firefox, browse to about:config and set the media.autoplay.enabled value to false.
-
WebXML test object (and, accordingly, XML checkpoints and output value steps)
See also: