Bug 60208 - FILTER / UI / VIEWING : Using autofilter, when filtering, merged cells related to row not drawn (second result onwards)
Summary: FILTER / UI / VIEWING : Using autofilter, when filtering, merged cells relate...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: AutoFilter Calc-Merge-Split
  Show dependency treegraph
Reported: 2013-02-03 00:08 UTC by dpnaessens
Modified: 2020-06-04 03:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Example File to demonstrate blank cells (12.32 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-02-03 01:20 UTC, dpnaessens
Screenshot of example file (104.47 KB, image/png)
2013-02-03 01:25 UTC, dpnaessens

Note You need to log in before you can comment on or make changes to this bug.
Description dpnaessens 2013-02-03 00:08:24 UTC
Where a spreadsheet has merged cells like below (as at step 2 below):

   A       B        C      D        E         F
1  |------|--------|-------|-------|--------|----------|
14 |      |        |       |       |--------|----------|
15 |      |        |       |       |--------|----------|
16 |------|--------|-------|-------|--------|----------|
31 |      |        |       |       |--------|----------|
32 |------|--------|-------|-------|--------|----------|
74 |------|--------|-------|-------|--------|----------|

And so on....

First row is frozen.

1) Auto filter all columns A-F on row 1
2) filter to a single/multiple value on say column F, which has no merged cells
3) Data in columns A -D will only be shown for the first row of merged
   cells (14-16), and rows with no merged cells (74).
   All other viewable rows containing merged cells are blank
   e.g. Rows 31-32 A-D merged cells will not be drawn/blank.
   Rows E-F are always shown correctly.

Sometimes scrolling the affected rows off the screen and back again
will cause those cells to be drawn, or F2/double click into A-D of a merged cell will cause that row to be redrawn and appear, though this can cause other previously shown cells to then go blank.
Comment 1 m.a.riosv 2013-02-03 01:05:28 UTC
Hi dpnaessens, thanks for reporting.

I can not see the issue.
Win 7x64 Ultimate
Versión (ID de compilación: 5b93205)

Please can you attach a file sample.
Comment 2 dpnaessens 2013-02-03 01:20:45 UTC
Created attachment 74112 [details]
Example File to demonstrate blank cells
Comment 3 dpnaessens 2013-02-03 01:25:39 UTC
Created attachment 74113 [details]
Screenshot of example file
Comment 4 dpnaessens 2013-02-03 01:26:57 UTC
Hi mariosv,

Attached example and screenshot of what happens for me.

If you filter on column O to say Test B or Test C,
I get the attached screenshot. If text is single line it appears,
but not for wrapped text.
Comment 5 A (Andy) 2013-03-29 15:42:23 UTC
reproducible with LO (Win7 Home, 64bit)
Comment 6 QA Administrators 2015-04-19 03:22:15 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2015-06-18 12:07:00 UTC

Win 7 Pro 64-bit Version:
Build ID: 437210d58f32177ef1829d704f7f4d2f1bbfbfdd
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-18_07:21:56
Locale: fi-FI (fi_FI)
Comment 8 QA Administrators 2016-09-20 10:10:18 UTC Comment hidden (obsolete)
Comment 9 m.a.riosv 2016-09-21 22:58:06 UTC
Still with:
Version: (x64)
Build ID: 3c2231d4aa4c68281f28ad35a100c092cff84f5d
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
Locale: es-ES (es_ES); Calc: group
Comment 10 QA Administrators 2018-06-04 02:34:21 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2020-06-04 03:44:13 UTC
Dear dpnaessens,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team