When a window is in a non-maximized state, going fullscreen and then toggling back 'returns' the window to a maximized state. Correct behaviour is returning to previous window size and position when not maximized at the time of going into fullscreen.
Works in 3.3.0, but bugging out already in 3.5.0. Lowered severity per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Ubuntu 14.10 64-bit Version: 4.5.0.0.alpha0+ Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-01-25_23:58:40 LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
I previously tagged this as preBibisect based on the reported versions, but in fact I can't reproduce it at all with Ubuntu 14.04 under lxde. Perhaps this is an interaction with a specific window manager. Would the original reporter and/or @Beluga please comment which desktop environment / window manager they are using, and whether it is a specific part of Libreoffice (Writer, Calc, Impress ...) they see the issue with, or all of them? Setting status to NEEDINFO - please set back to NEW when the requested information has been provided Thanks
Just vanilla Ubuntu, so Unity. Tested with writer.
Migrating Whiteboard tags to Keywords: (preBibisect) [NinjaEdit]
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Still repro (under KDE). Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: 3bc65fe56d726de2b6efe229daedb634df940ce8 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 26 December 2018
Dear Paul Reilly, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Paul Reilly, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to Matthew Francis from comment #2) > I previously tagged this as preBibisect based on the reported versions, but > in fact I can't reproduce it at all with Ubuntu 14.04 under lxde. Perhaps > this is an interaction with a specific window manager. > > Would the original reporter and/or @Beluga please comment which desktop > environment / window manager they are using, and whether it is a specific > part of Libreoffice (Writer, Calc, Impress ...) they see the issue with, or > all of them? > > > Setting status to NEEDINFO - please set back to NEW when the requested > information has been provided > > Thanks For me, using fvwm-crystal with fvwm3 and Xorg on gentoo, that have nothing to do with a specified windows manager, but all to do with ICCCM https://tronche.com/gui/x/icccm/ or, more presumably, the extended window manager hints EWMH https://www.freedesktop.org/wiki/Specifications/wm-spec/ With fvwm-crystal, I can maximize any windows in fullscreen with a simple key binding. To do that, fvwm tell X to remove the borders of the windows and to use the whole screen for that window. That work just fine, back and forth, with libreoffice - I use mostly writer. When a writer windows is into that maximized fullscreen mode, and I tell writer to go in fullscreen, it remove all its borders and menu. That also works just fine. The issue is than when going back from writer's fullscreen mode, libreoffice doesn't care about the precedent windows state, which was Maximized Fullscreen, and return into an annoying state whith a window bigger than the screen (of the size of the screen + the borders and title bar). At https://en.wikipedia.org/wiki/Extended_Window_Manager_Hints we can read than "The EWMH defines thirteen window state flags: ... Fullscreen: show the window fullscreen, ..." So for me, to say that, because some desktop handle it correctly, that's an issue with the other wm/desktop is a wrong clue, that because for all wm/desktops, the underlying process is the EWMH compliance of both the wm and the application. And yes, an user can use its wm to change the state of a given window and the application must understand that. In that case, the fullscreen mode of libreoffice make 2 things: it put the window into maximized fullscreen, which have to do with the EWMH compliance, and it remove the menu and other writer's bars, which have nothing to do with EWMH. The issue must be "just" the EWMH compliant part of that function. I also think it is great than the fullscreen function of the wm doesn't interfere with the libreoffice part of its fullscreen function, because that way One can have writer in maximize fullscreen all the time.