Description: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: No Additional Info: -
Created attachment 151659 [details] video of the jumping notebookbar
Confirming on Windows 10 Home with slight different visual glitch with the Tabbed Compact NB Version: 6.3.0.0.alpha1+ Build ID: 959e8ae7ea33ce94dd80ee8ea172b6db64593873 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Seems to be two issues here. 1.) the way os/DE handles the ">>" pop out toolbar holding the additional "hidden" NB controls. 2.) how the NB is refreshed when the pop out toolbar closes after a pick. The NB needs to be refreshed back to original view and button count--but instead keeps settings from when pop out was showing, and not all button controls are redrawn. Looking at Andreas' video, KDE packs the hidden items in a pop out that keeps the app frame's width. On Windows 10 w DWM the packing is a pop out that extends outside the LO App frame--may be nothing to be done about that. Action at close of the hidden button bar seems wrong bcz the Tabbed Compact NB does not return to its state before the hidden buttons were shown, and user has to resize to get the button controls to reappear to fit.
OK, so this does affect the Tabbed NB as well. It seems like the height of the pop out button bar includes pixels for a shadow. And that is applied to the gtk packing for the NB while the pop out is open. When closed it is not removed? And like Tabb Compact NB, until user resizes app frame removing the left over pixels from the shadow used on the pop out. But on the Tabbed NB, the refresh gets the width and count of buttons correct--just the height after redraw is wrong.
Dear andreas_k, 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
Issue of jumping NB still present, Tabbed NB and Tabbed Compact NB on Windows build of 7.2.2 Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
repro 24.2+ It is so slight for me that I don't even notice it, but it still is there...