[DesignerHost/HTML]: improve high-dpi screen behavior #19996
Conversation
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
handle previewer dpi changed event
|
You can test this PR using the following package version. |
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.
What does the pull request do?
Adds:
scaling, with a parameterscale.The parameter
scalewill be used to ensure the mouse events can be raised on the correct position.This can be used by the VSCode extension before sending a
ClientRenderInfoMessageto the DesignerHost.resize, with 2 parameterswidthandheight.This can be used to tell the new size of the canvas to the parent page, as when the iframe's content size changed, the iframe will not auto acquire the new size.
Fixs:
<body>added by the browser and some other change)What is the current behavior?
2025-11-05.170551.mp4
What is the updated/expected behavior with this PR?
ClientRenderInfoMessage.2025-11-05.170149.mp4
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Fixed issues