api.KeyboardEvent.repeat - Compatibility data may be outdated for chrome

[chris-sophos]

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Compat table states Chrome has partial support, citing a bug that appears to be resolved

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

Chrome listed as full support

Did you test this? If so, how?

Tested on Chrome on a Windows device, could not replicate the stated bug

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

https://issues.chromium.org/issues/40940886

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/repeat

MDN metadata

MDN page report details

• Query: api.KeyboardEvent.repeat
• Report started: 2025-08-21T06:20:56.267Z

[caugner]

Based on this comment in that Chromium bug, it looks like this was fixed in Chrome 137.

@chris-sophos Would you like to open a PR adding { version_added: 137 } below (making it an array)?

browser-compat-data/api/KeyboardEvent.json

Lines 1144 to 1148 in c61afe4

	"chrome": {
	"version_added": "32",
	"partial_implementation": true,
	"notes": "On Windows and Linux, if multiple keys are held down, a `keydown` event for the most recently pressed key will trigger with `repeat` incorrectly set to `false`. See [bug 40940886](https://crbug.com/40940886)."
	},

[chris-sophos]

Based on this comment in that Chromium bug, it looks like this was fixed in Chrome 137.

What about the notes regarding the Linux fix being reverted? The "Status Update" box seems to suggest it was fixed in Chrome 138
I'm not sure how to represent that 😅

[caugner]

What about the notes regarding the Linux fix being reverted?

Good question. Based on those comments, Linux under X11 has only been supported from Chrome 139. However, given that Wayland is now default on major distros, I would like to suggest that missing X11 support on longer justifies setting partial implementation (to be clarified with @ddbeck @Elchi3 @queengooborg), so I would just mention it in notes:

[
  { 
   "version_added": "137", 
   "notes": "Before Chrome 139, on Linux under X11, if multiple keys are held down, a `keydown` event for the most recently pressed key will trigger with `repeat` incorrectly set to `false`. See [bug 40940886](https://crbug.com/40940886)." 
 },
  { 
   "version_added": "32", 
   "version_removed": "137", 
   "partial_implementation": true, 
   "notes": "On Windows and Linux, if multiple keys are held down, a `keydown` event for the most recently pressed key will trigger with `repeat` incorrectly set to `false`. See [bug 40940886](https://crbug.com/40940886)." 
 }
]