-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Layout breaks on macOS with Amethyst #255
Comments
Thanks for posting, a couple of questions, that's the layout is mostly dictated by the browser.
Very timely as I'm about to redo the main layout (but the message layout is what gives you the issue). |
Closing due to lack of reproducibility. |
Also Fix #255 due to the large layout restructuring.
This should fix it. Verified with Firefox. Will land when the |
- Optima Layout: new Context based pluggable layout system - Now children have context functions, for better behaviors - Removed `store-applayout` - using withLayout on top-level Pages - ScrollToBottom: grounds-up subsystem for smooth scrolling with snap-to-bottom - Panes subsystem: use react-resizeable-panels together with our Panes subsystem - New: Split window chats, Drag to close windows, Button to split - using: https://github.com/bvaughn/react-resizable-panels - Cosmetic: Colors: update Light and Dark themes - Bootstrap Logic provider: will enable Mobile use cases - Removed NoSSR (the backend provided natually acts as the same) - Next load progress: loading indicator for slower pages (>300ms) - withLayout() system Additional benefits include: no-pluggable-flashing, pane-ready, fixed X-scrolling on Firefox, and more. Closes #308, #304, #255, #59. Progress on #305, #201, #296, #233, #208, #203.
Fixed on the |
Describe the bug
The page layout breaks when the windows are moved around with Amethyst on macOS. My setup is with two monitors, one of which is an ultrawide.
When switching modes (column, row, and so on), the content are is not rendered correctly, and the boundaries go out-of-screen. There is no way to revert - to the best of my knowledge - but to clean up the session and start from scratch.
Where is it happening?
Screenshots / context
The text was updated successfully, but these errors were encountered: