[Bug 159837] keyboard shortcuts don't work if style pane has focus
https://bugs.documentfoundation.org/show_bug.cgi?id=159837 --- Comment #4 from V Stuart Foote --- (In reply to V Stuart Foote from comment #3) oops s/MOD1/MOD2/ we're adding the MOD1 modifier to the existing MOD2 modifier for forwarding -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159837] keyboard shortcuts don't work if style pane has focus
https://bugs.documentfoundation.org/show_bug.cgi?id=159837 V Stuart Foote changed: What|Removed |Added Keywords||needUITest CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=43 ||822 --- Comment #3 from V Stuart Foote --- (In reply to Jim Raykowski from comment #2) > This also holds true for x11/win/qt5 VCL backends when focus is on any > toolbar item, for example, the save button in the standard toolbar, ironic! > > For me Gtk3 backend already works as expected. > > Here is a patch that makes these other backends also work as expected: > https://gerrit.libreoffice.org/c/core/+/163800 Thanks Jim, and that is ancient OOo era config to only handle the MOD1 modifier. So the not applicable to gtk3 backend seems to have obscured multiple WFM resolved issues, e.g. bug 43822--suspect there are a fair few to identify. Please push it and will test. @Cor, * heads up. =-STR-= +S as noted OP, or +w to close from TB 1. new writer document 2. dt for a para of text 3. to main menu 4. advance to standard TB 5. +w; result ??? alternate from SB decks 1. new writer document 2. dt for para of text 3. +4 to SB Navigator 4. + to move focus back from Page up to SB deck title 5. +w; result ??? 6. + to move focus to SB's tab bar 7. +w; result ??? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159837] keyboard shortcuts don't work if style pane has focus
https://bugs.documentfoundation.org/show_bug.cgi?id=159837 --- Comment #2 from Jim Raykowski --- This also holds true for x11/win/qt5 VCL backends when focus is on any toolbar item, for example, the save button in the standard toolbar, ironic! For me Gtk3 backend already works as expected. Here is a patch that makes these other backends also work as expected: https://gerrit.libreoffice.org/c/core/+/163800 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159837] keyboard shortcuts don't work if style pane has focus
https://bugs.documentfoundation.org/show_bug.cgi?id=159837 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||103459 CC||rayk...@gmail.com, ||samuel.mehrbrodt@allotropia ||.de, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Confirm STR. When F11 opens the Navigator SB deck, focus is on the style type tab bar of the Content panel. Default on opening lands on the Paragraph content panel. In that state, a +S shortcut does not function. Nor with any selection on the styles Tab bar. However, with advance into the Style listing to land pointer focus on a viable style, it allows the +S shortcut to fire and save. Similar mis-handling of the ^S shortcut when pointer focus is advanced by TAB out of the Styles content panel and onto the SB's Tab Bar. Seems an issue in the SB framework for handling the key? @Jim, Samuel ? =-testing-= Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bbc9ac1f08a5ee4b9f65eaf10110df328d95de95 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103459 [Bug 103459] [META] Sidebar UI and UX bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159837] keyboard shortcuts don't work if style pane has focus
https://bugs.documentfoundation.org/show_bug.cgi?id=159837 lvm changed: What|Removed |Added CC||lmiro...@yandex.ru See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||9135 -- You are receiving this mail because: You are the assignee for the bug.
