Web Recorder: Advanced Configuration and Troubleshooting

This article covers the Web Recorder's advanced controls: Custom Web Driver Profiles for shaping how the browser launches, the recorder's intelligent handling of URL entry, the global browser state, and a quick-reference table for common issues.

Custom Web Driver Profiles

A Custom Web Driver Profile is a JSON document of WebDriver capabilities that configures how the recorder browser is initialized. Reach for one when you need to:

• Set specific browser startup options (disable extensions, set the language)
• Apply custom proxy or network configurations
• Test with particular browser flags or experimental features
• Integrate with an external cloud browser provider

Applying a Profile to a Recording Session

In the Device Configuration dialog, toggle Custom Web Driver Profile ON, select a profile from the dropdown, and click Proceed. The profile applies to the current session, and an orange dot on the browser icon in the recorder header reminds you a profile is active.

What Device Simulation Overrides

When a profile is active, four attributes are always dictated by the recorder's Device Simulation selection, overriding any values in the profile: Device Width, Device Height, Device Pixel Ratio, and User-Agent-String. Everything else in the profile applies as configured. This keeps the emulated resolution you chose authoritative regardless of the profile's contents.

Managing Profiles

Create and manage profiles in Resources > Driver Profiles. Profiles are reusable across recording sessions and formal test runs. For the capability JSON in detail, see Web Driver Configuration for test executions (Profiles).

How URL Entry Is Recorded

When you enter a URL in the recorder's address bar, ACCELQ decides intelligently whether a browser-invoke statement belongs in your logic:

• Recorded: when the URL is loaded as part of creating a new Scenario in Design Studio, where invoking the browser is genuinely the first step of the flow.
• Not recorded: in every other case, such as returning to a Scenario from a previous session or reloading a page. A notification appears instead, with an Add Statement link so you can record the invocation deliberately if the flow calls for it, for example in a multi-application Scenario.
• Never when OFF: browser-invoke statements are not recorded with the recorder in the OFF state.

This prevents duplicate browser-invoke statements from routine navigation while keeping the choice in your hands.

The Browser Is Global to Your Project

The recorder browser is managed at a global level within the project. The same browser state (current page, cookies, session data) carries across whichever Scenario or Action you have open in the Logic Editor: navigate somewhere in one Action's editor, switch to another Action, and the browser is still there. This is by design, providing continuity when you develop multi-step flows across several Actions.

Troubleshooting Quick Reference