Bug 158347 - Incorrect table rendering if in merged heading cell split across pages
Summary: Incorrect table rendering if in merged heading cell split across pages
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-24 00:00 UTC by Alexander Kurakin
Modified: 2024-05-16 00:21 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Test case file (15.31 KB, application/vnd.oasis.opendocument.text)
2023-11-24 00:01 UTC, Alexander Kurakin
Details
Screenshot 1 (15.72 KB, image/png)
2023-11-24 00:01 UTC, Alexander Kurakin
Details
Screenshot 2 (17.95 KB, image/png)
2023-11-24 00:04 UTC, Alexander Kurakin
Details
Screenshot 3 (17.23 KB, image/png)
2023-11-24 00:05 UTC, Alexander Kurakin
Details
Screenshot 4 (23.90 KB, image/png)
2023-11-24 00:05 UTC, Alexander Kurakin
Details
Screenshot 5 (PDF exported) (57.54 KB, image/png)
2023-11-24 00:06 UTC, Alexander Kurakin
Details
Screenshot 1 (22.01 KB, image/png)
2023-12-19 17:32 UTC, Alexander Kurakin
Details
Screenshot 2 (24.55 KB, image/png)
2023-12-19 17:35 UTC, Alexander Kurakin
Details
Screenshot 3 (24.46 KB, image/png)
2023-12-19 17:40 UTC, Alexander Kurakin
Details
Screenshot 4 (32.91 KB, image/png)
2023-12-19 17:48 UTC, Alexander Kurakin
Details
Screenshot 5 (PDF exported) (69.12 KB, image/png)
2023-12-19 17:50 UTC, Alexander Kurakin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kurakin 2023-11-24 00:00:08 UTC
I made a table like:

-------------------------
|           |   |   |   |
------------| A | B | C |
| D | E | F |   |   |   |
--------------------------
| G | H | I | J | K | L |
          . . .
|-----------------------|

(The  first two lines are header.)

If I put a page break inside the table, I see the artifacts.
Also there are artifacts on PDF export.

See the test case file and the screenshots.
Comment 1 Alexander Kurakin 2023-11-24 00:00:50 UTC
Reproduced in:

Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: ru-RU (ru_RU.UTF-8); UI: ru-RU
Gentoo official package
Calc: threaded
Comment 2 Alexander Kurakin 2023-11-24 00:01:15 UTC
Created attachment 191009 [details]
Test case file
Comment 3 Alexander Kurakin 2023-11-24 00:01:50 UTC Comment hidden (obsolete)
Comment 4 Alexander Kurakin 2023-11-24 00:04:36 UTC Comment hidden (obsolete)
Comment 5 Alexander Kurakin 2023-11-24 00:05:00 UTC Comment hidden (obsolete)
Comment 6 Alexander Kurakin 2023-11-24 00:05:37 UTC Comment hidden (obsolete)
Comment 7 Alexander Kurakin 2023-11-24 00:06:26 UTC Comment hidden (obsolete)
Comment 8 m_a_riosv 2023-11-24 00:06:33 UTC
Looks like a duplicate of tdff#154312
Comment 9 Alexander Kurakin 2023-11-24 00:09:05 UTC
(In reply to m.a.riosv from comment #8)
> Looks like a duplicate of tdff#154312

Bug #154312 is about selection.
This bug #158347 is about lines.
Comment 10 Alexander Kurakin 2023-11-24 00:14:51 UTC Comment hidden (obsolete)
Comment 11 m_a_riosv 2023-11-24 00:50:26 UTC
No issue for me with 
Version: 7.6.4.0.0+ (X86_64) / LibreOffice Community
Build ID: 3e180c01f0d304c7b19b623c083a1634079d5c87
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Version: 7.5.9.1 (X86_64) / LibreOffice Community
Build ID: 2f04f73a0f4ebfe9735ca11da23d6ed8f830fe34
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
with or without skia.

Please test with skia enable. Menu/Tools/Options/LibreOffice/View
or updating LibreOffice version
or updating the graphics driver.
Comment 12 Alexander Kurakin 2023-11-24 16:22:45 UTC
(In reply to m.a.riosv from comment #11)
> No issue for me with 

Did you move the table up and down? I made the screenshots at the different positions.

Also you can change the 1st, 2nd and 3rd columns' widths to get more artifacts.
Comment 13 Buovjaga 2023-12-19 16:38:00 UTC
(In reply to Alexander Kurakin from comment #10)
> Screenshot 1: thick extra line, thin extra line
> Screenshot 2: the same
> Screenshot 3: thick extra line, thin extra line, thick extra line
> Screenshot 4: thin "line" instead of real thick line
> Screenshot 5: the same

I don't understand what the problem is. Can you explain what you mean by artifacts? Maybe you could mark them with red circles in a screenshot? I tested and I don't see anything wrong.

Arch Linux 64-bit, X11
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b731cdfbd74a61ff389f479ae4cb4dcf261b1ccf
CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 19 December 2023
Comment 14 Alexander Kurakin 2023-12-19 17:32:10 UTC
Created attachment 191508 [details]
Screenshot 1

> I don't understand what the problem is. Can you explain what you mean by artifacts? Maybe you could mark them with red circles in a screenshot?

Sure.

Screenshot 1.

1.1. Why does this black line exist?
Is it from the header? Then, where are there three columns of the second header row?
Or, it's from the first non-header row (see also Screenshot 4, Screenshot 5.)

1.2. Why does this gray line exist?
Comment 15 Alexander Kurakin 2023-12-19 17:35:46 UTC
Created attachment 191510 [details]
Screenshot 2

Screenshot 2.

2.1. Ok, it is from the header at this screenshot.
Should be the 1st row of the header be repeated on the second page?

2.2. Why does this gray line exist? (See also Screenshot 4, Screenshot 5.)
And, should be the 1st row of the header be repeated on the second page?
Comment 16 Alexander Kurakin 2023-12-19 17:40:00 UTC
Created attachment 191511 [details]
Screenshot 3

Screenshot 3.

3.1. See 2.1.

3.2. See 2.2.

3.3. Why does this black line exist?
Is it from the first non-header row (see also Screenshot 4, Screenshot 5)? Why?
Comment 17 Alexander Kurakin 2023-12-19 17:48:46 UTC
Created attachment 191512 [details]
Screenshot 4

Screenshot 4.

4.1. What's going here?
4.1.a. Why does this gray line exist? See also 1.2.
4.1.b. See 2.2.b.
4.1.c. Are the header and non-header rows intersected? See also 3.3.b.

4.2. Are the header and non-header rows intersected? See also 4.1.c.
Comment 18 Alexander Kurakin 2023-12-19 17:50:24 UTC
Created attachment 191513 [details]
Screenshot 5 (PDF exported)

Screenshot 5.

The same as Screenshot 4.
Comment 19 Buovjaga 2023-12-19 18:35:49 UTC
(In reply to Alexander Kurakin from comment #14)
> Created attachment 191508 [details]
> Screenshot 1
> 1.2. Why does this gray line exist?

View - Table Boundaries
Comment 20 Alexander Kurakin 2023-12-19 19:44:15 UTC
So, there      (In reply to Buovjaga from comment #19)
> (In reply to Alexander Kurakin from comment #14)
> > Created attachment 191508 [details]
> > Screenshot 1
> > 1.2. Why does this gray line exist?
> 
> View - Table Boundaries

Thanks. Strange but true.
Then don't uderstand: why on the second page, only?
Comment 21 Alexander Kurakin 2023-12-19 19:44:22 UTC
So, globally there are two main issues.

*THE FIRST ISSUE*. None of these statements are true:
A: The-first-page-header is visually equal to the-second-page-header.
B: The-second-page-header is the visual rest/residue of the-first-page-header.

*THE SECOND ISSUE*. The header rows and the non-header rows are visually intersected.
Comment 22 Armondo Lopez 2024-04-13 17:45:55 UTC
Thank you for submitting the bug. I can confirm that it is present in 

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

and

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 23 Stéphane Guillou (stragu) 2024-05-15 17:01:56 UTC
A report should be about a single issue, and you are describing several here.

I think the main issue here is that you have a table that has headings in the the two first rows, but your table properties only use 1 row for "Text flow > Repeat heading"
Please test again with 2 rows for "Repeat heading", and open a new report for a single issue you notice - if there is any left.
(Sorry to be closing as "invalid", but if we are hoping to have issues resolved, we need to have clear, focused reports - I hope it makes sense!
Comment 24 Alexander Kurakin 2024-05-15 18:02:52 UTC
(In reply to Stéphane Guillou (stragu) from comment #23)
> I think the main issue here is that you have a table that has headings in
> the the two first rows, but your table properties only use 1 row for "Text
> flow > Repeat heading"
> Please test again with 2 rows for "Repeat heading", and open a new report
> for a single issue you notice - if there is any left.

Yes, you're right - isn't left.

Is it root of the bug? The single (well, double) bug - "Incorrect rendering (and unable to select) of 2-rows table heading with vertically merged cells".

Thanks!
Comment 25 Stéphane Guillou (stragu) 2024-05-15 23:51:55 UTC
(In reply to Alexander Kurakin from comment #24)
> (In reply to Stéphane Guillou (stragu) from comment #23)
> > I think the main issue here is that you have a table that has headings in
> > the the two first rows, but your table properties only use 1 row for "Text
> > flow > Repeat heading"
> > Please test again with 2 rows for "Repeat heading", and open a new report
> > for a single issue you notice - if there is any left.
> 
> Yes, you're right - isn't left.
> 
> Is it root of the bug? The single (well, double) bug - "Incorrect rendering
> (and unable to select) of 2-rows table heading with vertically merged cells".
> 
> Thanks!
The selection issue is bug 154312 I think, as m_a_riosv mentioned.
The rendering issue I guess is LO understandably struggling to know what to do with a two-row header with merged cells that the user wants to repeat only the first row of across two pages... There might be better ways to deal with that special case, so if you think of one, please state clearly in a new report:
- what the (single) issue is, with steps and illustration
- what you think a better solution would be

Thank you!
Comment 26 Alexander Kurakin 2024-05-16 00:21:38 UTC
(In reply to Stéphane Guillou (stragu) from comment #25)
> The selection issue is bug 154312 I think, as m_a_riosv mentioned.

> (In reply to m.a.riosv from comment #8)
> > Looks like a duplicate of tdff#154312
> 
> Bug #154312 is about selection.
> This bug #158347 is about lines.

> > I think the main issue here is that you have a table that has headings in
> > the the two first rows, but your table properties only use 1 row for "Text
> > flow > Repeat heading"
> > Please test again with 2 rows for "Repeat heading", and open a new report
> > for a single issue you notice - if there is any left.
> 
> Yes, you're right - isn't left.

And bug #154312 isn't about headers...
Funny if they're the same.