https://bugs.documentfoundation.org/show_bug.cgi?id=168503

Michael Weghorn <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #4 from Michael Weghorn <[email protected]> ---
(In reply to Callegar from comment #0)
> Actual Results:
> Both None and Color (or some other entry) is selected
> 
> Expected Results:
> Either None or some other entry should be selected

attachment 202932 shows what it looks like for me with LibreOffice 25.8.1 as
packaged in Debian testing. It's similar with the gen VCL plugin.

It's indeed a little confusing, but as I understand it, these are 2 different
highlightings (with a different shade shade of blue being used with the Breeze
style):

1) The darker blue one for "Colour" indicates the currently active option.
2) The slightly lighter blue one for "None" indicates the current keyboard
focus.

Pressing the Tab key repeatedly will move 2) forward, while 1) remains
unchanged.

It would probably make sense to have 2) match 1) initially if keyboard focus is
on one of those buttons.

However, I don't see this with current master any more, because the initial
focus when opening the dialog is on the vertical tab control.

-> Can we close this as WORKSFORME, as it's not a problem in master?
(The switch to vertical tabs is a larger change and cannot be backported to
25.8.)

Version: 25.8.1.1 (X86_64) / LibreOffice Community
Build ID: 580(Build:1)
CPU threads: 32; OS: Linux 6.16; UI render: default; VCL: kf6 (cairo+wayland)
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Debian package version: 4:25.8.1-1
Calc: threaded

Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4e6d5774d97a19cfe3160df94cc2e8733794d4cf
CPU threads: 32; OS: Linux 6.16; UI render: default; VCL: qt6 (cairo+wayland)
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to