Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SafariDriver, Key Presses & Glass Panes #75

Open
lolaodelola opened this issue May 8, 2024 · 1 comment
Open

SafariDriver, Key Presses & Glass Panes #75

lolaodelola opened this issue May 8, 2024 · 1 comment

Comments

@lolaodelola
Copy link

A SafariDriver-managed Safari session rejects external interaction, however in order for the AT-Driver protocol to perform actions like a user does (whether via simulated key presses or via higher-level "user intentions"), the glass pane may need to be "selectively permeable".

Background

As a security mechanism, Safari installs a transparent “glass pane” over the automation windows while the browser is being used for WebDriver testing. This pane catches any stray interactions (mouse, keyboard, resizing, and so on) that could affect the automation window. If a running test gets stuck, you can interrupt it by “breaking” the glass pane and stopping the session. When an automation session is interrupted, the test’s connection to the browser is permanently severed, and the automation window remains open for further inspection, until closed manually.

@lolaodelola lolaodelola transferred this issue from w3c/aria-at-automation-driver May 8, 2024
@sadym-chromium
Copy link

Minutes from WebDriver BiDi WG 2024-05-08: https://www.w3.org/2024/05/08-webdriver-minutes.html#t04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants