Description: Floating toolbar opens with wrong size. Moving the float down a bit will resize it correctly when the mouse pointer enters a tool element box. - It will not resize if the float is moved around high on screen, only if moved below the dock list region. - It will not resize until the mouse pointer enters a tool element box, regardless of where on screen the float is. - Correct size of floating toolbox does not persist to restart of writer or re-open of document. attaching wrong and correct size screenshots Resizing height/width layout of floating toolbar does not persist, but position persists. Floating toolbar defaults to min height max width with wrong size every time write is restarted or document reopened. Have seen automatic float toolbar resizing hide buttons and misbehave in other such ways. But this was easy to reproduce for me. Steps to Reproduce: 1. drag out a floating toolbar 2. close and re-open writer or document 3. toolbar opens with wrong size 4. drag floating toolbar below docklist position 5. move mouse cursor inside any tool button 6. toolbar correctly resizes Actual Results: toolbar opens with wrong size resizes correctly if positioned below dock list and mouse pointer moved into a tool button box Expected Results: toolbar should open with correct size preferably remember height & width settings from before Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.3 (x64) Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: default; VCL: win Locale: en-US (en_SE); UI: en-US Calc: threaded
Created attachment 164550 [details] floating toolbar opens too large
Created attachment 164551 [details] resizes correctly when dragged below dock list and mouse pointer enters any tool button box
I can't confirm it with Version: 7.0.0.3 (x64) Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded
Not reproduced. I'm wondering how in your screenshot the toolbar appears above the menu and title bars. I am unable to undock it into that position. netjiro: can you test again with version 7.1? Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: bdbb5d0389642c0d445b5779fe2a18fda3e4a4d4 CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear netjiro, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear netjiro, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp