MicrosoftEdge
[Feature]: Add Flag to Suppress Fullscreen and Pointer Lock Prompts
Describe the feature/enhancement you need
The Fullscreen API and Pointer Lock API display prompts reminding users that they can press ESC to unlock cursor, exit Fullscreen etc. For our use case this is problematic and breaks immersion.
The scenario/use case where you would use this feature
We use the Construct 3 game engine to design 3D first person games that make use of the Fullscreen API and Pointer Lock API. The popups that appear when these methods are used are immersion breaking and frustrating for players.
How important is this request to you?
Impactful. My app's user experience would be significantly compromised without it.
Suggested implementation
A simple flag, e.g. --disable-prompts would be invaluable to us.
What does your app do? Is there a pending deadline for this request?
Our app is a 3D first person game built using the Construct 3 engine. Countless other games built in the engine have this issue.
This is coming up as a blocker for some people to move from NW.js to WebView2 - it's coming up on our forum in a few places (e.g. https://www.construct.net/en/forum/construct-3/how-do-i-8/rid-pointer-lock-messages-184857, https://www.construct.net/en/forum/construct-3/how-do-i-8/construct-exporting-webview2-184888).
This is one of those things where the wrapper application already has permission to do something like pointer lock without any notification appearing, so there is no security/usability benefit in the context of WebView2, it's just an annoying and unnecessary message. Hoping it's a straightforward one to do and that it can be addressed soon!
This is a major issue for us as well. Our game is mouse based and every time the user switches to a new menu a prompt is shown, which is preventing us for switching to WebView2 until this issue is fixed.
Thank you for bringing this to our attention. This issue is now part of our backlog. We will update you once development begins.
Thank you for bringing this to our attention. This issue is now part of our backlog. We will update you once development begins.
@Lakshmisha-KS Is this issue being overlooked? Hoping it's a straightforward one to do and that it can be addressed soon!
