Bug 134777 - EDITING: After adding content to new cells while leaving an empty row after the old content, rerunning autofilter has no effect
Summary: EDITING: After adding content to new cells while leaving an empty row after t...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoFilter
  Show dependency treegraph
 
Reported: 2020-07-13 11:18 UTC by Johnny Rosenberg
Modified: 2025-02-23 20:26 UTC (History)
2 users (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 Johnny Rosenberg 2020-07-13 11:18:14 UTC
An example:
1. Start with an empty spreadsheet.
2. In column A, enter the following on the first few rows:
MyHeader
A

B
C

A
A
C
B

3. Select column A and click Data→AutoFilter
4. Click the auto-filter drop-down.
5. Tick or untick as follows, then click OK:
☒ (empty)
☒ A
☐ B
☒ C
6. All rows in which the column A cell contains B are hidden.
7. Enter B somewhere in the A column, at one or more rows.
8. Click the autofilter drop-down again. All selections are already what we want, so just click OK.
9. Nothing changed.

Expected result (at step 9):
The same as in step 6.

One workaround is to just select something else, hit OK, then click the drop-down and do step 5 again, but that's annoying if you have to do it often.

I think this bug has always been there, but I'm not sure. I run LibreOffice 6.4.4.2 on Manjaro Linux 20.0.3 at home and a slightly older version of LibreOffice on Windows 10 at work, not sure exactly which one (and I can't check since I'm on vacation, but it's 6.4.something). Both have the same problem.
Comment 1 SteveDee 2020-08-10 09:44:24 UTC
I have found that if you follow steps 1 through 8 and a cell is left empty between the original entries and extra entries, then a bug occurs, ie. step 9

I can confirm that this is present in the following builds:

Version: 6.4.5.2 (x64)
Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: en-AU (en_US); UI-Language: en-GB
Calc: CL


Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-AU (en_US); UI: en-GB
Calc: CL

However, if the cell is not left empty between entries, then this WORKSFORME
Comment 2 sora34ce 2020-08-11 17:51:43 UTC
I actually realized that while it doesn't work for rows placed after the initial set, it does work with the ones between the initial set's contents. I'm using version 7.1.0.0, so I have no idea if this works for any other version. As SteveDee says, it varies: it WORKSFORME in some areas but the error is still there in others
Comment 3 sora34ce 2020-08-11 17:52:33 UTC
Of course this isn't assuming it doesn't work in other columns. We need extra testing if that's the case
Comment 4 Buovjaga 2021-02-22 16:46:29 UTC
Repro. Let's assume that we want the empty row taken into account.

Arch Linux 64-bit
Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: dec32864a61104001cb6ff63c218ea5fb2a7ab1e
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 22 February 2021
Comment 5 QA Administrators 2023-02-23 03:25:11 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2025-02-23 03:11:11 UTC Comment hidden (obsolete)
Comment 7 Johnny Rosenberg 2025-02-23 20:26:14 UTC
It seems to work better now, but if I, in my example, add one or more B at least two rows below the rest of the used rows, those are not hidden by the AutoFilter, so it seems like even if I selected the whole column before creating the AutoFilter, it doesn't care about the rows below the first empty row after the last entry.
So as I said, it works better now, but I'm not sure if I would say it works perfectly. I guess running into the problem now is much less likely now than before, at least.