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