Summary: | Firefox always openes non-fullscreen | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Henning <boredsquirrel> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | minor | CC: | nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Henning
2023-08-04 16:31:35 UTC
When you say fullscreen, do you actually mean fullscreen, or do you mean maximized? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I mean maximized. I always click on their CSD "fullscreen" button and have it in fullscreen. But "macos ugly like" it always opens vertically fullscreen, horizontally with a bit of space. It never seems to remember my sizing. Is this something Firefox has to change or Plasma can enforce? So my fix was to set the programs window properties to "vertically maximised" and "horizontally maximized". But in a former issue I already mentioned how extremely confusing the "set window properties" dialog is (hard to find, unclear whats given properties and whats wanted properties) We could fix this in KWin by fixing Bug 437089, or you would report this in Firefox and they could fix it themselves by setting a real maximized state when they save their window state. *** This bug has been marked as a duplicate of bug 437089 *** |