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 may not recognize which is the latest version.

Other Firefox add-ins and the Add-ons Manager
  • We recommend disabling other Mozilla Firefox add-ins when performing tests of your Web application or Web page.

  • If you have the Add-ons Manager enabled, in the Web tab of the Run and Record Settings dialog box, if you set Firefox to open to a specific URL, Firefox does not open to the specified URL at the beginning of a recording or run session.

    Workaround: Disable the Add-ons Manager before using Firefox.

User Account Control enabled

If you are working on a computer where the UAC (User Account Control) option is set to ON, UFT does not support testing on Mozilla Firefox browsers that were installed (or upgraded to a new version) after you installed UFT.

Workaround: After installing Mozilla Firefox on the environment described above, log in as an administrator and open UFT.

This enables UFT to install files that are required for Mozilla Firefox support.

Anonymous content elements

UFT 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.

Standard dialog boxes in Firefox

Mozilla Firefox uses different standard dialog boxes than the Windows standard dialog boxes used by Microsoft Internet Explorer.

  • If you create steps on such dialog boxes, you should create additional steps to be used when running on Mozilla Firefox, and precede them with an If statement to check which browser is running.
  • 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.

For example, see Sample standard dialog boxes in Internet Explorer and Firefox.

Privileged URLs

If you are testing on a Firefox version 57 and higher, a Firefox limitation prevents you from navigating to privileged URLs.

UFT 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.

Sample standard dialog boxes in Internet Explorer and Firefox

The following two dialog boxes are a security alert of the same Web site. The one on the left is from Microsoft Internet Explorer, and the one on the right is from Mozilla Firefox. Although they both look like a Windows dialog box, the Mozilla Firefox one is actually a browser window.

Back to top

Legacy agent

The legacy Functional Testing Agent for Firefox is found at <UFT installation folder>\Installations\Firefox\AgentLegacy.xpi and has the following known issues:

  • Firefox versions. The legacy Functional Testing Agent for Firefox is supported only for Firefox versions 39 and earlier.

  • Operating systems. The legacy Functional Testing Agent for Firefox may experience unexpected results on a Windows 8 operating system.

Troubleshooting the legacy agent

If you are using the legacy Functional Testing Agent for Firefox, and UFT is unable to recognize a Firefox object, run Firefox in compatibility mode and try again. For example:

  1. Enable Firefox compatibility mode, selecting Windows XP.

  2. Restart Firefox and try to recognize the object again in UFT.

Back to top

Recording

Prerequisites

Recording on Mozilla Firefox pages is only possible when the page is fully loaded.

Unsupported methods and features while recording
  • When accessing FTP servers using Mozilla Firefox, UFT does not record actions on the server authentication dialogs.

  • UFT does not record steps performed on browser dialog boxes (such as alert, confirmation, or prompt) if these dialog boxes are opened in a new browser tab.
  • When recording on Mozilla Firefox, UFT does not use the location identifier to learn the object..

  • Low-level recording is not supported on Firefox.

  • The Active Screen captures still images only when recording in Firefox.

    To use Active Screen right-click options, such as adding steps or checkpoints, record your tests in Internet Explorer instead.

  • SAPUIList.SetItemData. To record on an input field in a list, click the field twice during recording before entering text.
  • The following methods are not supported for recording on Mozilla Firefox:

    Browser.Home

    Browser.FullScreen

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 enters the search string but does not perform the search.

Workaround: Do one of the following:

  • When recording the search operation, click the search button instead of pressing Enter.

  • Manually add the Submit (or Click) step to the test or component.

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.

Back to top

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 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
  • If you drag and drop a tab to create a new window in Firefox, UFT stops recognizing, recording, or running any web objects in the new window.
  • When recording a test on a Web page coded in languages other than HTML5, drag and drop methods can be recorded in Internet Explorer only.
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.

Java applets

If you need to test Java applets in Mozilla Firefox browsers, you must use the legacy Functional Testing Agent for Firefox.

This agent is found in the <UFT installation folder>\Installations\Firefox folder. For more details, see Legacy agent.

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:

  1. In Firefox, native to about:config.

  2. Search for security.csp.enable.

  3. Change the value to false.

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

UFT does not support accessing browser dialog boxes (such as alert, confirmation, or prompt) directly in Mozilla Firefox.

Workaround: Use the HandleDialog or GetDialogText methods described in the Web section of the UFT Object Model Reference for GUI Testing.

If the Browser("xxx").Dialog("xxx").Page("xxx") object is recognized, either use a recovery scenario with the HandleDialog method, or a Browser("xxx").Dialog("xxx").Page("xxx").Type step to handle the pop-up dialog box.

For example, use an Enter key to click the default button and close the dialog box.

Note: If you are working in Firefox version 57 or higher, the GetDialogText and DialogExist 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.

  • Modal or modaless dialog boxes

  • ViewLink test object

  • 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)

Back to top

See also: