Disable browser's context menu on screen canvas#1584
Closed
chschnell wants to merge 1 commit into
Closed
Conversation
Contributor
|
Wasn't this fixed in the |
Contributor
Author
|
I didn't know, I'll close this then. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When absolute mouse positioning is enabled we no longer lock the mouse pointer to the screen canvas. This leads to the browser's context menu now popping up when right-clicking the canvas, hiding the guest's context menu underneath.
This PR fixes that by disabling the browser's context menu entirely on the canvas. I figured that we don't ever want to see it on the canvas (dosen't matter if relative or absolute positioning is enabled), is that ok or are there any exceptions I should consider?