fix: use native WebView zoom so zoomed pages fit the window
Facebook Messenger on your desktop, without the Facebook clutter
Brought to you by:
kristoffer-r
Menu
▾
▴
#324 fix: use native WebView zoom so zoomed pages fit the window
closed
nobody
None
2026-10-17
2026-10-16
Anonymous
No
Originally created by: kristofferR
Zooming in (Cmd/Ctrl + +) clipped the right and bottom edges of Messenger and could push the message input below the window. Carrier zoomed with CSS zoom on the document (a body transform on Windows), which scales Messenger's viewport-sized layout past the window instead of shrinking the viewport it lays out into.
This switches page zoom to the native WebView zoom (WKWebView pageZoom, WebKitGTK zoom level, WebView2 ZoomFactor), as proposed in [#250]:
- Rust applies the zoom on window creation, on each Messenger page load, on settings changes, and immediately on the page's
carrier:zoomevent (persisting stays coalesced as before). No new command is exposed to the remote page. - The page no longer touches CSS; it only tracks the level and reports keyboard/menu zoom steps.
- The CSS-zoom compensation in Hide Names and the scheduled-send composer is removed, since bounding rects are no longer scaled, along with the browser-test cases that simulated CSS zoom.
Checked on Linux: native 150% zoom reports an 800×520 layout viewport in a 1200×780 window, so Messenger reflows to fit. macOS and Windows still need a manual pass (keyboard steps, Settings zoom select, new windows, theme recreation).
Related
Originally posted by: coderabbitai[bot]
⚠️ Action not completed
Review rate limited. > Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.Originally posted by: coderabbitai[bot]
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
❤️ Share
Comment
@coderabbitai helpto get the list of available commands.Related
Commit: [975f45]
Originally posted by: chatgpt-codex-connector[bot]
Codex Review Summary
This comment shows the latest Codex review activity on this pull request.
26d09d0ℹ️ About Codex in GitHub
[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review" or "@codex security review". Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.
Originally posted by: chatgpt-codex-connector[bot]
Codex Review: Didn't find any major issues. Hooray!
Reviewed commit:
af209fcccdℹ️ About Codex in GitHub
[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Originally posted by: chatgpt-codex-connector[bot]
Codex Review: Didn't find any major issues. Bravo.
Reviewed commit:
26d09d069bℹ️ About Codex in GitHub
[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Ticket changed by: kristofferR