Bug 161513 - Change buttons in AutoFilter dialogue to double-clickable buttons
Summary: Change buttons in AutoFilter dialogue to double-clickable buttons
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.8.0.0 alpha0+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoFilter
  Show dependency treegraph
 
Reported: 2024-06-11 15:37 UTC by Jürgen Kirsten
Modified: 2025-12-01 10:58 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Kirsten 2024-06-11 15:37:27 UTC
Description:
The AutoFilter dialogue box has two buttons that change the selection of items with a single click. The 'Show only the current item' and 'Hide only the current item' buttons could be changed to a button with a double-click option.
If you use one of the two buttons and want to perform the action in exactly the same way, it would be a relief to be able to do it with a double-click.

Steps to Reproduce:
Create a table and use the AutoFilter. Open the dialogue! If you have different entries, you can quickly adjust the selection with the buttons "Show only the current item" and "Hide only the current item".

Actual Results:
After clicking on one of the buttons, you must click OK again.

Expected Results:
It would be desirable if this could be achieved with a double-click.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
-
Comment 1 Roman Kuznetsov 2025-10-25 14:00:01 UTC
So, the main goal here is to have the effect in place without OK pressing?

Added the UX-team
Comment 2 Heiko Tietze 2025-10-27 09:06:37 UTC
What problem would be solved by merging the buttons? Perhaps to save space. But it comes on cost of simplicity as the toggle button (double click would be very unusual and hard to figure out for average users) needs a third state that applies after any other selection. And I don't understand these two options as flavors of one action, thinking of a label or tooltip that makes the functionality clear to users.
Comment 3 Jürgen Kirsten 2025-10-30 11:31:01 UTC
(In reply to Roman Kuznetsov from comment #1)
> So, the main goal here is to have the effect in place without OK pressing?
> 
> Added the UX-team

Yes, that is the goal. Clicking OK can be omitted by double-clicking, as there is virtually nothing else to do after clicking on "Show only the current item" or "Hide only the current item".
Comment 4 Jürgen Kirsten 2025-10-30 11:35:35 UTC
(In reply to Heiko Tietze from comment #2)
> What problem would be solved by merging the buttons? Perhaps to save space.
> But it comes on cost of simplicity as the toggle button (double click would
> be very unusual and hard to figure out for average users) needs a third
> state that applies after any other selection. And I don't understand these
> two options as flavors of one action, thinking of a label or tooltip that
> makes the functionality clear to users.

Hi Heiko, my suggestion was not to merge the two buttons. That would indeed be very opaque. No, my suggestion is that by double-clicking on one of the two buttons "Show only the current item" or "Hide only the current item" you can execute the action directly without having to click OK again.
Comment 5 Heiko Tietze 2025-11-04 15:19:07 UTC
Double-click a toggle button is very uncommon. I don't know any application that does similar. Users cannot know - and it's somewhat tricky to implement (or make it consistent) as to my knowledge buttons don't fire a double click event and we have to evaluate a single click against previous events. Position, and time would play a role, meaning you probably accept a second click on the same control not the very same position, and accept a second click after a certain time span (which OS typically allow to alter, for example to support accessibility). I recommend to abstain from such interaction.
Comment 6 Heiko Tietze 2025-11-14 08:19:11 UTC
We discussed this topic in the design meeting.

The envisioned double-click on the toggle buttons would override the default behavior, thus hard to figure out for users. And the benefit is marginal - you do not frequently open the widget, click on show or hide, and submit via okay. It's more typical to interact with the checkbox list after a show/hide preselection.

The verdict was to not recommend such change. But first to make sure we do not miss a use case that deserves improvement.
Comment 7 Jürgen Kirsten 2025-11-16 14:37:25 UTC
(In reply to Heiko Tietze from comment #6)
> We discussed this topic in the design meeting.
> 
> The envisioned double-click on the toggle buttons would override the default
> behavior, thus hard to figure out for users. And the benefit is marginal -
> you do not frequently open the widget, click on show or hide, and submit via
> okay. It's more typical to interact with the checkbox list after a show/hide
> preselection.
> 
> The verdict was to not recommend such change. But first to make sure we do
> not miss a use case that deserves improvement.

Hello Heiko,

It's great that you've discussed this topic. If you don't think it's very useful, that's a shame. I think it would be good, which is why I suggested it.

Just to clarify one thing. In my opinion, it doesn't matter whether all users understand it. The button should work as before with a simple click and enable interaction. Only if you don't want to make any further changes should you use a double-click. That's what I meant by my suggestion. All computer users are familiar with this behaviour, e.g. from File Explorer or Nautilus. Here, you can click on a file to view its properties. Double-clicking opens the file with the default program. This is a relatively good comparison to the auto-filter buttons.

Liebe Grüße
Jürgen
Comment 8 QA Administrators 2025-11-25 15:37:25 UTC Comment hidden (obsolete)
Comment 9 Heiko Tietze 2025-12-01 10:58:50 UTC
(In reply to Jürgen Kirsten from comment #7)
> All computer users are familiar with this behaviour ... click on a file
> to view its properties. Double-clicking opens the file...
But that's a listview not a button.

The same is true for icons on your desktop - it is a list of items that allows to select one (or many) items via single click and execute the action per double click. On many operating systems / desktop environments it is configurable or even the default to execute on single click to support motorically impaired users. 

I do not know any application that toggles a button via single click and executes some action on double click.