-
Notifications
You must be signed in to change notification settings - Fork 104
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
Chromium unmaximises when focus is lost #3592
Comments
Hmm. Reverting chromium (to 127.0.6533.72) fixes the behaviour |
Merged
Saviq
added a commit
that referenced
this issue
Sep 27, 2024
Enhancements: . Allow to specify an app id for when running on the wayland platform #3614 Bugs fixed: . SIGSEGV on input device disconnection #3601 . Frame fails to enforce fullscreen on wpe-webkit-mir-kiosk #3600 . Chromium unmaximises when focus is lost #3592 . Apps constantly resizing #3573 . Our fork/exec spawning is unsafe #3494 . Revert "Fix random leak" #3609 . Smoke tests are failing #3610
Saviq
added a commit
that referenced
this issue
Sep 27, 2024
Enhancements: . Allow to specify an app id for when running on the wayland platform #3614 Bugs fixed: . SIGSEGV on input device disconnection #3601 . Frame fails to enforce fullscreen on wpe-webkit-mir-kiosk #3600 . Chromium unmaximises when focus is lost #3592 . Apps constantly resizing #3573 . Our fork/exec spawning is unsafe #3494 . Revert "Fix random leak" #3609 . Smoke tests are failing #3610
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Under a Mir server (
miral-app
ormiriway
)Run the chromium snap on Wayland
Maximise it (e.g. double click titlebar)
Start another all (
Ctrl-Alt-T
)Expect: app (terminal) appears, chromium remains maximised
Actual: app (terminal) appears, chromium is unmaximised
The text was updated successfully, but these errors were encountered: