Bug 159737 - Autofilter dropdown should be case-sensitive and independent from the filter dialog
Summary: Autofilter dropdown should be case-sensitive and independent from the filter ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoFilter
  Show dependency treegraph
 
Reported: 2024-02-15 16:29 UTC by Kevin Suo
Modified: 2024-03-01 10:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample Document (11.68 KB, application/vnd.oasis.opendocument.spreadsheet)
2024-02-16 18:38 UTC, Rainer Bielefeld Retired
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2024-02-15 16:29:08 UTC
Steps to Reproduce:

1. Type in the following data in Calc.

Letter	Number
a	1
A	2
b	3
B	4

2. Set autofilter, click on the autofilter dropdown in column "Letter.

Current Result:
The dropdown shows two entries: lowercase "a" and lowercase "b".

Expected Result:
The dropdown should show four entries: "a", "A", "b", "B".

Already a bug in 
Version: 7.4.0.0.alpha1+ / LibreOffice Community
Build ID: 45613274794636ba98d0e978fe872511297d275d
CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN
Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN
Calc: threaded

and also exists on today's master.
Comment 1 Kevin Suo 2024-02-15 16:38:42 UTC
Already a bug in
Version: 5.4.0.0.alpha1+
Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3; 
Locale: zh-CN (zh_CN.UTF-8); Calc: group

("oldest" in the bibisect-linux-64-6.0 repo)

I don't think it's worth bibisecting anymore, removing "bibisectRequest" keyword.
Comment 2 Mike Kaganski 2024-02-15 17:00:59 UTC
> ("oldest" in the bibisect-linux-64-6.0 repo)
> 
> I don't think it's worth bibisecting anymore, removing "bibisectRequest"
> keyword.

I don't quite see the logic here. We can bibisect up to 4.something. *If* this is a regression (an old version worked OK), *then* respective keywords (including bibisectRequest) are needed.
Comment 3 Kevin Suo 2024-02-15 17:02:16 UTC
It seems that the behaviour in AutoFilter uses the case-sensitive settings in the "Data > Standard Filter > Options" dialog. Case-sensitive is unchecked by default in the standard filter dialog.

Autofilter is different from standard filter. It should always use "case-sensitve".
Comment 4 Kevin Suo 2024-02-15 17:04:26 UTC
(In reply to Mike Kaganski from comment #2)
> *If* this is a regression (an old version worked OK), *then* respective keywords (including bibisectRequest) are needed.

Re-added "bibisectRequest".
Comment 5 ady 2024-02-16 00:16:06 UTC
This has always been the behavior since LO 3.3. Yes, the case-sensitivity behavior in AutoFilter follows the Options setting in/for the Standard Filter.

I am not saying whether this is an incorrect behavior or not. I am just stating the fact. So, without any consideration on that regard (i.e. bug or not), this behavior is inherited. It can also be replicated on a recent LO 24.8 alpha, and also in AOO 4.1.15.
Comment 6 Mike Kaganski 2024-02-16 04:18:13 UTC
Note that the bug 106047 (that I added to See Also) explicitly fixed a *case sensitivity* in non-ASCII case; so please note that at least some people do not agree with "It should always use "case-sensitve"" statement.

Since people might want case-insensitive behavior, and it is configurable now (using Standard Filter setting), my take is:

1. WONTFIX / NOTABUG;
2. Alternatively, a description is needed, when current behavior is problematic (e.g., a use case, when Standard Filter needs to be case-insensitive, but autofilter must be case-sensitive);
3. And last, the configuration could be moved to some more logical place, and (if #2 is provided) split into two separate configurations (UX).
Comment 7 Heiko Tietze 2024-02-16 12:49:29 UTC
I don't see a setting somewhere else not being properly shown to the user as a solution. But I also believe that case-sensitivity is nothing that needs to be added to the autofilter dialog.
Comment 8 Rainer Bielefeld Retired 2024-02-16 18:38:28 UTC
Created attachment 192610 [details]
Sample Document

It's not "Always lowercase a". 
Seems to be "the case that appeared first / most top" in the column
Comment 9 Rainer Bielefeld Retired 2024-02-16 18:43:51 UTC
I did some tests and found the same behavior in the 2 other Spreadsheet applications I tested:
a) SoftMaker PlanMaker
b) Cryptpad <https://cryptpad.disroot.org/sheet/#/2/sheet/edit/vPD7SQiqbsZvSzZEMWWMgdrD/>
Comment 10 Heiko Tietze 2024-03-01 09:39:02 UTC
We discussed the topic in the design meeting.

Both the hidden relation to the filter dialog option as well as an extra option on the floating autofilter dialog is bad. 

Based on the idea that users might be not aware of uppercase character/word if we hide it we should always show case-sensitive (alpha and Alpha being visible) allowing to uncheck items manually. MSO Excel does the same. 

Not really what is requested. If you accept, Kevin, please change the summary.
Comment 11 Kevin Suo 2024-03-01 10:24:07 UTC
(In reply to Heiko Tietze from comment #10)

> Based on the idea that users might be not aware of uppercase character/word if we hide it we should always show case-sensitive (alpha and Alpha being visible) allowing to uncheck items manually. MSO Excel does the same. 

That is exactly what I mean in comment 0.