feat(api): add logical monitor bounds to the Monitor object - #15520
Merged
Conversation
polw1
force-pushed
the
feat/monitor-logical-bounds
branch
from
June 13, 2026 02:09
13d4dca to
f1a1676
Compare
Replaces the logicalPosition/logicalSize/logicalWorkArea fields with JSDoc on Monitor.size, Monitor.position and Monitor.workArea stating the values are in physical pixels, including examples converting to the logical pixels expected by window creation options.
polw1
force-pushed
the
feat/monitor-logical-bounds
branch
from
June 13, 2026 02:14
f1a1676 to
8cf8fb8
Compare
Contributor
Package Changes Through 8cf8fb8There are 7 changes which include tauri-utils with patch, tauri-runtime-wry with patch, tauri with patch, @tauri-apps/api with patch, tauri-bundler with patch, tauri-cli with patch, @tauri-apps/cli with patch Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
Legend-Master
approved these changes
Jun 13, 2026
Legend-Master
left a comment
Legend-Master
left a comment
Contributor
There was a problem hiding this comment.
The documentations should help a lot on this, thanks!
Proksima
pushed a commit
to Proksima/tauri
that referenced
this pull request
Aug 5, 2026
…ps#15520) * feat(api): add logical monitor bounds to the Monitor object * docs(api): document physical pixel units on Monitor fields Replaces the logicalPosition/logicalSize/logicalWorkArea fields with JSDoc on Monitor.size, Monitor.position and Monitor.workArea stating the values are in physical pixels, including examples converting to the logical pixels expected by window creation options. * fix monitor position example null check
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.
Adds
logicalPosition,logicalSizeandlogicalWorkAreato theMonitorobject returned bycurrentMonitor(),primaryMonitor(),monitorFromPoint()andavailableMonitors().The values are derived in
mapMonitor()from the existing physical bounds viatoLogical(scaleFactor), so they match the logical units expected byWebviewWindowcreation options. This removes the need for manual physical-to-logical conversion in userland, which is easy to miss on macOS mixed-DPI setups.Existing
position,size,workAreaandscaleFactorfields are unchanged, so the change is non-breaking.closes #15519