Repository navigation
Kai Code: Only allow the expanded widget on viewports with room for it - #174
Merged
boehlerlukas merged 1 commit intoOct 9, 2026
Conversation
The expanded messenger (max-width 690px, no height cap) was allowed on any viewport of 451px or more. On a phone with the page zoomed out just past the mobile breakpoint (e.g. a 571px-wide CSS viewport), the widget left the full-screen mobile layout, and a stored "expanded" choice made it `calc(100% - 40px)` wide and nearly full height, covering almost the whole page. Expansion now needs a viewport of at least 768px (`widgetExpandMinWidth` in UI.js), used by both the expanded CSS media query and `GleapFrameManager.canExpandWidget()`, so they stay in sync. Narrower viewports show the default 410px widget, hide the expand button, and keep the stored preference for when the window gets wider again. Added tests for 571px, a fractional 767.5px, and the 768px boundary. Gleap ticket #185052.
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
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.
Automated changes by Kai Code.
The expanded messenger (max-width 690px, no height cap) was allowed on any viewport of 451px or more. On a phone with the page zoomed out just past the mobile breakpoint (e.g. a 571px-wide CSS viewport), the widget left the full-screen mobile layout, and a stored "expanded" choice made it
calc(100% - 40px)wide and nearly full height, covering almost the whole page.Expansion now needs a viewport of at least 768px (
widgetExpandMinWidthin UI.js), used by both the expanded CSS media query andGleapFrameManager.canExpandWidget(), so they stay in sync. Narrower viewports show the default 410px widget, hide the expand button, and keep the stored preference for when the window gets wider again. Added tests for 571px, a fractional 767.5px, and the 768px boundary.Gleap ticket #185052.
Gleap ticket: View in Gleap