Created attachment 169391 [details]
autofilter

(In reply to Peter S Anderson from comment #1)
> Hi Petr,
> Would you please send us a spreadsheet which behaves as you describe.
> Thanks…..Peter.

Of course. Any Calc file.
But I see one interesting thing:

In KDE: It's OK only with KDE integration pack (I don't use it because I cannot use Unicode commands for inserting characters)
In Cinnamon: bug in any case.

Repro with file, but only with gtk3

Arch Linux 64-bit
Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: dcce840cb2383873cc77da04b0bdc4526042c212
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 14 February 2021

(In reply to Buovjaga from comment #5)
> Repro with file, but only with gtk3
> 
> Arch Linux 64-bit
> Version: 7.2.0.0.alpha0+ / LibreOffice Community
> Build ID: dcce840cb2383873cc77da04b0bdc4526042c212
> CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
> Locale: fi-FI (fi_FI.UTF-8); UI: en-US
> Calc: threaded
> Built on 14 February 2021

Yep, as I said, in KDE no problem but only with kde-integration pack installed. Using this pack is problematic (bug #140251).

Looking at gtk3-demo and glade where there is a treeview with such toggle buttons in them I don't find cases where clicking on the text auto-toggles the toggle button so the defacto expectation for that toolkit doesn't seem to be to auto-toggle in this case. Though its probably possible to bodge it in some way. (FWIW keyboard "space" will toggle them)

Sorry, tdf#116675 is only for generic vcl plugin, i don't know how to implement the same for gtk.

A related change is: tdf#139115 what limit this 1-click-toggle behaviour to a very few treelists.
Also added an other behaviour, the 2 clicks to toggle (first only select, second toggle), but i think it is not used anywhere yet.
All other treelist will toggle only with the checkbox.

A quick search for "set_clicks_to_toggle" in the code, shows it is used only in 4 places.

Dear Petr Valach,

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