Web Recorder

Overview

The Web Recorder v1 is a tool integrated into the Script Editor to capture user interactions within web applications. Web scripts recorded with the new Web Recorder use Playwright. This version supports a subset of actions and is optimized for browser-based apps. Some features are still under development, and limitations are described in the related section.

• For general information on the Script Recorder and related use cases, see Using the Script Recorder.

• For an overview of Playwright functions, the specific commands used to automate and interact with web applications using Web Recorder v1, see Web Recorder Functions (Playwright). In most cases, you do not need to work with those functions directly if the recording plays back successfully as captured. That page is intended primarily as an advanced reference for users who need to review, adjust, or extend recorded functions.

Getting Started

Download the latest Script Editor package containing the Web Recorder v1 from your admin or setup email. For details, see Downloading and installing the Script Recorder.

Creating a New Application

1. In Login Enterprise Script Editor, click Create a new Login Enterprise Application.

2. Click the three-dot icon to the right of Save as, choose a folder for the script, and enter a file name.

3. In the Select application type, select Browser application.

4. Next to Use new web recorder script template, enable the toggle to use Web Recorder, which creates the web script in Playwright format.

5. In the URL, enter the start page of your web application.

6. In the Browser, select your preferred browser, e.g., Chrome.

7. In Browser arguments (Optional), configure how the browser starts by entering command-line arguments, if needed. For example, you can add flags to enable specific features or disable extensions. For more information, see Using Browser Arguments via a Magic Comment.

8. In Profile location (Optional), enter a custom path for storing the browser profile if your environment requires centralized management or compliance-related configurations. Otherwise, leave this field blank.

9. Click Create to generate the script template. Once the template is created, the Record button appears; click it to start the new recording session.

Starting the Recording: Recording the Script

In the Script Editor top menu, click Record to start the recording.

When the recording starts, a player opens where you can perform actions.

The web page must be DOM-ready before the Recorder can highlight UI elements. Once it is, the Recorder draws green borders around the elements so you can see which ones you're recording.

Web Recorder supports the following actions:

• Mouse scroll

• Left click

• Right-click (Browser context menu clicks are not supported)

• Double-click

• Typing and special keys (Enter, arrows, etc.)

• Hover actions using the hotkey Alt + H

• Browser JavaScript popups (alert, confirm, prompt)

• Interactions within iFrames

• Browser arguments

When hover capture is enabled, all hover events are recorded until you disable it. Use this feature carefully, as there are no visual indicators when it is active. Hovering over an element before enabling the hotkey will not capture it; you must move away and back.

You can adjust waits and timeouts after the recording is complete and before generating the script. By default, the recorder applies a 2-second wait and a 5-second timeout to each step. You can change these default values in the General Settings, or modify them per action.

Stopping the Recording: ScriptResultWindow

When you stop the recording, the ScriptResultWindow shows an overview of all recorded steps (before generating the script, right after the recording was stopped).

In the Overview screen, you can adjust Settings, export the script as JSON, and generate the script to run it.

Settings

General

Action

When you open an action step, the settings are shown automatically. Action steps can use global settings or custom settings:

• Global settings: The action step uses the global settings. The settings are read-only and can't be changed in the action step.

• Custom settings: The action step uses custom settings. Select this option to make the fields available for editing in the action step.

Editing an Action Name

You can change the name of each action to make it more descriptive. The action name is shown in the script as a comment before the corresponding step.

To edit an action name:

1. Hover over the action.

2. Select the pencil icon.

3. Enter a new name.

4. Click Submit.

Selector

When you record actions, the Recorder detects the underlying DOM structure and generates selector candidates to identify each web element.

The Recorder checks these candidates against the page layout and automatically assigns the first option that matches exactly one element, using this priority order:

1. test-id: Dedicated automation attributes (like data-testid). Most stable.

2. id: The element's unique HTML ID.

3. form: Form-specific attributes (name, placeholder, or for).

4. href: The hyperlink destination URL (links only).

5. accessibility: Labels used by assistive tech (aria-label, alt, or title).

6. general: The shortest unique CSS path.

7. attr: CSS paths using generic attributes. Most brittle; used as a last resort.

You can choose or override the selector while the recording is paused, then test whether the selected selector resolves to the intended element.

Filtering During Recording

The Recorder automatically discards unstable data during recording, including session-randomized IDs (such as :r1:), state classes (such as -hover or -active), and direct clicks on icons inside buttons (the Recorder automatically targets the parent button instead).

Element Resolution During Playback

During test playback or when using the Test button, the Engine uses a fallback chain to locate the element, stopping at the first step that finds a single match:

1. Inner text alone: If the text is unique, the selector is ignored entirely. The Test button follows the same resolution logic as playback, so the test result should match what the generated script will do.

2. Selector alone: Used if the text matches multiple elements.

3. Selector + inner text combined: Used if steps 1 and 2 are both ambiguous.

4. Partial selector + inner text: The final fallback strategy.

Inner Text

The innerText refers to the text content within a web element. The Engine uses it during playback in the following ways:

• Recording tiebreaker: If no selector candidate is unique on its own (a candidate matches two or more elements), the Engine automatically uses the element's innerText as a tiebreaker to find a unique match.

• Playback step 1: During test execution or when you click the Test button, the Engine evaluates the innerText alone first. If the text is completely unique on the page, the Engine matches the element immediately and does not evaluate the selector.

Running the Script

1. In the ScriptResultWindow, click Generate script.

2. Copy the generated script to the clipboard:

3. Paste the copied script into the Script Editor:

4. In the Script Editor top menu, click Run to run the script.

The script should be available under the Debug Output tab:

For more information on using this part of the Recorder, see Debugging with Script Editor.

Exporting the Script as JSON

This option provides additional information on script failures, facilitating feedback submission and analysis.

Importing the Script as JSON

Alternatively, if you already have an existing script recording (JSON file), click Import recording in the Script Editor top menu and proceed with the steps described above.

Restrictions and Limitations

Recommendations

Tutorials

Using Browser Arguments via a Magic Comment

You can pass arguments to the browser by using a magic comment in your script. This allows you to control how the browser behaves during recording and playback.

The most common use cases include:

• Recording and playing back web applications in incognito or private mode.

• Recording and playing back with the browser window maximized.

This feature also supports any other valid browser arguments.

How to Use

Insert the magic comment at the top of your script with the appropriate browser arguments. See the screenshot below for an example.

Examples

Chrome

--incognito --start-maximized

Edge

--inprivate --start-maximized