[🐛 Bug]: Unable to send proper key event for \u2019 (keycode empty)

[reece-white]

What happened?

Issue:
The keyboard shortcut on macOS to enable firefox picture-in-picture mode is command + Shift + option + ]. In JavaScript these are dispatched as 3 KeyboardEvents: 'Meta/Command', 'Alt', 'Shift', '’'. The ’ key is sent with a combination of option/alt + ]. It is impossible to send this combination using WebDriver.

Steps to reproduce:
await action.keyDown(Key.ALT).sendKeys(']').keyDown(Key.COMMAND).keyDown(Key.SHIFT).perform();

Expected result:
Picture in picture launched in Firefox
A trusted KeyboardEvent is dispatched that looks like:

isTrusted: true
altKey: false
bubbles: true
cancelBubble: false
cancelable: true
charCode: 0
code: "BracketRight"
composed: true
ctrlKey: false
currentTarget: null
defaultPrevented: false
detail: 0
eventPhase: 0
isComposing: false
key: "]"
keyCode: 221
location: 0
metaKey: false
repeat: false
returnValue: true
shiftKey: false
sourceCapabilities: InputDeviceCapabilities {firesTouchEvents: false}
srcElement: body
target: body
timeStamp: 61259.80000001192
type: "keyup"
view: Window {window: Window, self: Window, document: document, name: '', location: Location, …}
which: 221
[[Prototype]]: KeyboardEvent

Actual events:
action.sendKeys(Key.ALT).sendKeys('’').perform()

isTrusted: true
altKey: false
bubbles: true
cancelBubble: false
cancelable: true
charCode: 0
code: ""
composed: true
ctrlKey: false
currentTarget: null
defaultPrevented: false
detail: 0
eventPhase: 0
isComposing: false
key: "’"
keyCode: 0
location: 0
metaKey: false
repeat: false
returnValue: true
shiftKey: false
sourceCapabilities: InputDeviceCapabilities {firesTouchEvents: false}
srcElement: body
target: body
timeStamp: 4728.29999999702
type: "keydown"
view: Window {window: Window, self: Window, document: document, name: '', location: Location, …}
which: 0
[[Prototype]]: KeyboardEvent

---

action.sendKeys(Key.ALT).sendKeys(']').perform()

isTrusted: true
altKey: true
bubbles: true
cancelBubble: false
cancelable: true
charCode: 0
code: "BracketRight"
composed: true
ctrlKey: false
currentTarget: null
defaultPrevented: false
detail: 0
eventPhase: 0
isComposing: false
key: "]"
keyCode: 221
location: 0
metaKey: false
repeat: false
returnValue: true
shiftKey: false
sourceCapabilities: InputDeviceCapabilities {firesTouchEvents: false}
srcElement: body
target: body
timeStamp: 4046.5
type: "keydown"
view: Window {window: Window, self: Window, document: document, name: '', location: Location, …}
which: 221
[[Prototype]]: KeyboardEvent

How can we reproduce the issue?

const { Builder, Key, By, until } = require('selenium-webdriver');

(async function example() {
    let driver = await new Builder().forBrowser('firefox').build();
    try {
        await driver.get('http://developers.canal-plus.com/rx-player/');
        await driver.wait(until.elementLocated(By.className('choice-input-button')), 10000);
        // To see the event in the console
        await driver.executeScript(() => {
            window.addEventListener('keydown', (e) => {
                console.log(e);
            });
        });
        await driver.findElement(By.className('choice-input-button')).click()
        // Wait for video to start
        await driver.sleep(5000);
        await driver.actions().keyDown(Key.ALT).keyDown(Key.COMMAND).keyDown(Key.SHIFT).sendKeys('\u2019').perform()
        await driver.sleep(15000);
    } finally {
        await driver.quit();
    }
})();

### Relevant log output

```shell
No log

Operating System

macOS Monteret

Selenium version

^4.8.0

What are the browser(s) and version(s) where you see this issue?

Chrome 110, Firefox 109

What are the browser driver(s) and version(s) where you see this issue?

geckodriver 0.32.0, ChromeDriver 109.0.5414.74

Are you using Selenium Grid?

No response

[github-actions]

@reece-white, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[titusfortner]

It's up to Mozilla which keyboard shortcuts are going to be supported in geckodriver; I would reach out to them to see if it is something they want to accommodate.

[github-actions]

Hi, @reece-white.
This issue has been determined to require fixes in GeckoDriver.

You can see if the feature is passing in the Web Platform Tests.

If it is something new, please create an Issue with the GeckoDriver team.

Feel free to comment the issues that you raise back in this issue. Thank you.

[reece-white]

It's up to Mozilla which keyboard shortcuts are going to be supported in geckodriver; I would reach out to them to see if it is something they want to accommodate.

@titusfortner Thanks for the quick reply. However this is not just observed in Firefox using geckodriver. I was able to reproduce the KeyboardEvent not firing correctly in Chrome 110 with chromedriver as noted in the issue (although there is no behavioural output displayed like the picture-in-picture for firefox).

[titusfortner]

Selenium properly sends the keys to the driver. What the drivers do with those keys is based on what the browser vendors support. There's nothing to change in the Selenium code that will affect the results you want.

[reece-white]

Thanks, issue raised with geckodriver: mozilla/geckodriver#2084