Bug 278652 – [GTK] keydown/up gives outdated modifier state

• Component: WebKitGTK
• Status: NEW

[Roope Salmi]

Created attachment 472297 [details]
Example HTML demonstrating the issue

Ubuntu 22.04.4
WebKitGTK 2.44.2-0ubuntu0.22.04.1 or local build @ https://commits.webkit.org/281240@main

Example HTML (attached):

<script>
    window.addEventListener("keydown", (e) => {
        document.body.innerHTML = `keydown ${e.ctrlKey} ${e.altKey} ${e.shiftKey}`;
    });
    window.addEventListener("keyup", (e) => {
        document.body.innerHTML = `keyup ${e.ctrlKey} ${e.altKey} ${e.shiftKey}`;
    });
</script>


Press one of the modifier keys down and up, and observe the text.

Actual behavior on GTK4:

1. Press Ctrl down
2. Text is "keydown false false false"
3. Release Ctrl
4. Text is "keyup true false false"

Actual behavior on GTK3:

1. Press Ctrl down
2. Text is "keydown true false false"
3. Release Ctrl
4. Text is "keyup true false false"

Expected behavior:

1. Press Ctrl down
2. Text is "keydown true false false"
3. Release Ctrl
4. Text is "keyup false false false"

[Roope Salmi]

Also applies to event.getModifierState()

[Roope Salmi]

Another tangentially related issue is that the modifiers are not updated in PointerEvents when a pointer lock is active.