Known Issues - Mozilla Firefox

General

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

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

  • UFT does not support anonymous content elements in non-XUL frames. (For example, the buttons in the Mozilla Firefox SSL exception page.)

  • We recommend disabling other Mozilla Firefox add-ins when performing tests of your Web application or Web page.

  • The SAP WDJ Add-in is not supported on Firefox browsers.
  • 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.

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

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

    For example, 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.

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

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

  • 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

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

  • When recording steps in Mozilla Firefox, additional steps may be recorded.

    Workaround: Manually remove the extraneous steps after the recording session ends.

  • Low-level recording is not supported on Firefox.

  • The following methods are not supported for recording on Mozilla Firefox:

    • Browser.Home

    • Browser.FullScreen

  • 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.
  • 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"/>) and not if it is assigned as a property (for example, aObj.onclick = function() {some code})

  • The Active Screen is not supported for use with Mozilla Firefox browsers.

  • UFT does not record steps performed on browser dialog boxes (such as alert, confirmation, or prompt) if these dialog boxes are opened from a new browser tab.

  • When recording on Mozilla Firefox, UFT does not use the location identifier to learn the object..

  • When accessing FTP servers using Mozilla Firefox, UFT does not record actions on the server authentication dialogs.

Back to top

Test Objects, Methods, Properties, and Checkpoints

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

    Workarounds for Firefox only:

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

  • The Object Spy and Checkpoint Properties dialog boxes do not retrieve the current value of edit boxes in Mozilla Firefox dialog boxes.

  • The Object Spy and Navigate and Learn dialog boxes do not retrieve the current value of tabmodal dialogs in Mozilla Firefox.

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

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

  • The following test objects, methods, and other Web-specific functionalities are not supported in Firefox:

    • iFrame (with a Javascript source) and Frameset objects are not supported in Mozilla Firefox browsers.

    • Firefox Start Page

    • about://* pages

    • Modal or modaless dialog boxes

    • ViewLink test object

    • WebXML test object (and, accordingly, XML checkpoints and output value steps)

    • Browser.Object method

    • Browser.Stop

  • Text area checkpoints are not supported on Mozilla Firefox.

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

  • If you need to test Java applets in Mozilla Firefox browsers, you must use the legacy Functional Testing Agent for Firefox, found in the <UFT installation folder>\Installations\Firefox folder. For more details, see Legacy agent.

  • If you take a snapshot of an ASPAjaxRichTextArea object on FireFox, it might not be displayed correctly in the Active screen.

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

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

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

Back to top

See also: