Steps to reproduce in Writer: 1) Open a text document 2) Open Sidebar (Menu > View > Sidebar) 3) Click on Page deck tab 4) Click in Format panel Width spin box 5) Move mouse pointer over tab bar 6) Use mouse wheel to show a different deck Result: Cursor is hid in Width spin box. Test this by pressing up and down keys and observing document view width change. Expected results: Mouse wheel does not change visible deck so focus is not hid.
I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 31d3369803ce4eceab5ef708f2cd33748b6d10ea CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Hi Jim, Could you please try in master again ?
Created attachment 149034 [details] bug demo Hi Xisco, Thanks for trying to repro. I still reproduce using Version: 6.3.0.0.alpha0+ Build ID: ee3cf6c82747385a1466cde66598d8e92859c904 CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded I've attached a video demonstration. Notice that keyboard focus and cursor is hid in Page deck Format panel Width spin box when deck is changed to Gallery deck using mouse wheel positioned on sidebar tab bar. This allows page width to be sized using up and down arrow keys. Tab key will change hidden focus to Height spin box which can then be sized with up and down arrow keys. While making the video demonstration I noticed tab key navigation shows combo box outlines from Page deck on top of Gallery deck. This is due to focus still in Page deck.
Repro. This started when the decks started responding to the mouse wheel (5.1). Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: e77beebb0d839f5dc0d4f9c4fd7cc9b7ccfd0175 CPU threads: 8; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 16 February 2019
One way to fix this would be to revert the patch that introduced scroll wheel functionality to the sidebar tab bar. commit 8c5e922d66d154405029380374f088cee6578056 Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>, Wed Oct 28 01:58:43 2015 +0100 (3 years, 4 months ago) Committer: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>, Wed Oct 28 02:11:58 2015 +0100 (3 years, 4 months ago) Follows: libreoffice-5-0-branch-point Precedes: libreoffice-5-1-branch-point Branches: <Expand> handle scrollwheel events in TabBar of Sidebar - using the scrollwheel in the TabBar used to scroll the document: - even though the deck next to it handles scroll event on its own - thus there are two areas that arent even touching (separated by the deck) scrolling the same area - instead, now we capture mousewheel scrolls and switch through the decks of the sidebar. This should also severely simplify navigating them. Change-Id: Ie2136f4ec67dedf72ff6b56d16356f6a12de74ea
Dear Jim Raykowski, 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
Still able to repro Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: ad5df52e03056eb5b8f5267a26a4191286342d21 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Still reproduced in: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 24087697d5cf78aac346d4dcea0596373e15a95c CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded