CEF 109 requestPointerLock() results in Chromium bug

[chocolatemelt]

Describe the bug Attempting to request pointer lock on any element inside a CEF application running CEF109 or earlier results in the following logged to console:

Uncaught (in promise) DOMException: If you see this error we have a bug. Please report this bug to chromium.

To Reproduce Steps to reproduce the behavior:

1. Run a CEF109 application
2. Attempt to call requestPointerLock on an element

Expected behavior Pointer lock is requested and the cursor will remain inside the element.

Screenshots

Versions (please complete the following information):

• OS: Windows 11
• CEF Version: 109

Additional context We run an application that currently can't be upgraded past 109 (Windows 7/8/8.1 support). I'm not sure if this issue is fixed in later versions of CEF or if it's completely unsupported; any info on this would be appreciated. I've done considerable digging in the forums and on the Chromium issue tracker for this, but don't see much useful information on it. I saw that CEF previously didn't implement it, but I noticed that it is an available function to call (albeit with the bug mentioned).

I'm using the code in this codepen to test the functionality, so it should work otherwise (it seems to work in regular modern Chrome browsers without issues): https://codepen.io/dextero/pen/jOEQayG

Thanks!

[chocolatemelt]

for what it's worth, totally okay with patching our CEF109 if it's a fix that's introduced in a later CEF; otherwise happy to stop investigating entirely if it's not fully supported at all

[magreenblatt]

Please only report bugs for supported versions.