Created attachment 173544 [details] Screenshot of the floating UNO-Inspector window The UNO object inspector tool, activated from menu Tools > Development Tools, starts as a panel at the bottom of the main window, like the sidebar. Like the sidebar (and many toolbars), this inspector panel can be dragged by mouse and undocked from the main window, becoming a floating window. However, unlike the sidebar, the behavior of the inspector window after undocked is rather strange and causes UX problems. 1. Too easy to undock. The inspector panel doesn't have a obvious "title bar" like the sidebar which is used for dragging and undocking. Instead, it seems the whole area from "Current Selection" to "Class Name: foo" can be used to drag the panel off its place. I first found this undocking behavior by accidentally triggering it when trying to highlight the class name with mouse (for copying) . 2. The undocked floating inspector window has a sub-optimal size, and many elements are not displayed by default. The user has to enlarge the window to see everything that was shown at the docked panel status. See attached screenshot. 3. Hard to re-dock. The undocked sidebar can be relatively easily re-docked by dragging the floating window towards the right edge of the window. However, once the inspector window is undocked, the user has to drag it very precisely to the center of the bottom edge just above the status bar -- a tiny area -- in order to re-dock it as a panel. I'm not sure this undocking of UNO inspector is intentional, but currently as is, it doesn't seem to be useful. Please either disable this undocking or improve its behavior when undocked. The bug was first found in 7.2.0 Beta1, and is still reproducible in 7.2.0 RC1: Version: 7.2.0.1 (x64) / LibreOffice Community Build ID: 32efc3b7f3a71cfa6a7fa3f6c208333df48656cc CPU threads: 2; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: en-US Calc: threaded
Repro NixOS Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: b1df9c67349cf4cc5be4128d797aefb87f50e38f CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: x11 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
*** Bug 143669 has been marked as a duplicate of this bug. ***
Repro Version: 7.3.8.0.0+ (x64) / LibreOffice Community Build ID: e1ad83ddb2f39419fb5d7c69eba51e2b9f49c788 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: CL Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community Build ID: c94961c6869c34b3874d21cfaa5ec1488609acfe CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: CL Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1c629ca0048670db4bed5e7d8d76bcf8e81f2158 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: CL threaded
For this version of LibreOffice, the UNO object inspector tool is directly a floating window: Version: 7.6.0.0.beta1+ (X86_64) / LibreOffice Community Build ID: 1b5cee822e0bc15ddbdfc86926678ca35ab3e082 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: fr-FR (fr_FR); UI: en-US Calc: CL threaded
Dear Ming Hua, 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