Bug 131126 - WRITER: Numbering should be separate for table columns and inserting a new row shouldn't increase number in vertically merged cell where rows don't change
Summary: WRITER: Numbering should be separate for table columns and inserting a new ro...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables Bullet-Number-Outline-Lists
  Show dependency treegraph
 
Reported: 2020-03-04 14:50 UTC by Timur
Modified: 2024-08-12 03:13 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Test ODT (11.63 KB, application/vnd.oasis.opendocument.text)
2020-03-17 08:43 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2020-03-04 14:50:57 UTC Comment hidden (me-too)
Comment 1 Timur 2020-03-04 14:55:18 UTC
Description:
Numbering is wrong for table columns, also for vertically merged cells.

Steps to Reproduce:
    1. Create a new document in LibreOffice Writer and insert a table with 2 columns and 9 rows.
    2. Merge vertically 3-3 rows in the first column like this: 1-2-3, 4-5-6, and 7-8-9.
    3. Insert numbering in A: the 3 merged cells or B: in all cells.
    4. Move the text cursor to the first cell with the numbering and insert a new row in the table by right clicking on Table > Insert > Rows below

Actual Results:
In 3. numbers in the left merged cells are A: 1., 4., 7. or  B: 1., 7., 13. 
After 4. numbers in the left merged cells are A: 1., 5., 8. or  B: 1., 9., 15. 

Expected Results:
In 3. numbers in the left merged cells are: 1., 2., 3. and in B: numbers are from 1 to 9.
After 4. numbers in the left merged cells in A remain:  1., 2., 3. and in B: numbers increase from 1 to 10.

See attachment 154824 [details] with test compared OO LO MSO.

Note: there was a fix 
https://git.libreoffice.org/core/commit/3a69e1a6b8eab79c55b6e8f3edd2ee2da45b39c0 in bug 123102 but didn't affect this.
Comment 2 Dieter 2020-03-16 09:45:09 UTC Comment hidden (obsolete)
Comment 3 Heiko Tietze 2020-03-17 08:16:05 UTC Comment hidden (obsolete)
Comment 4 Dieter 2020-03-17 08:36:32 UTC
(In reply to Heiko Tietze from comment #3)
> Can we make this a duplicate? It's likely a facet of one of these reports:
> 
> bug 129989 - Inserting a row in a table resets list numbers
> bug 100643 - Numbering of rows in tables changes on horizontal split of
> neighbouring cells

I don't think, that this is a duplicate, but part of the broader topic "Numbering in tables"

> See also 
> 
> Bug 115930 - [META] Adding and deleting cells / rows / columns

I thought about a new Meta-Bug "Numbering in Tables"

> If not, please share a test document as I cannot follow the numbers. No idea
> if this should be an enhancement.

Simply do this
1. Create a table with two columns and some rows
2. Mark first column and add numbering
3. Mark second column and add numbering

Result: Numbering of first column changes
Enhancement: Give possibility to number table per column
Comment 5 Timur 2020-03-17 08:43:26 UTC
Created attachment 158737 [details]
Test ODT

This is a clear bug, per test ODT and  attachment 154824 [details] that shows proper behavior by MSO.
Comment 6 Heiko Tietze 2020-03-17 08:55:53 UTC
(In reply to Dieter from comment #4)
> Result: Numbering of first column changes
> Enhancement: Give possibility to number table per column

Something like Table > Properties > Text Flow: 

Numbering sequence: (o) Row ( ) Column

(In reply to Timur from comment #5)
> This is a clear bug, per test ODT and  attachment 154824 [details] that
> shows proper behavior by MSO.

No idea how to restart numbering comprehensible. It would break the Table > Properties approach.
Comment 7 Dieter 2020-03-17 09:05:25 UTC
(In reply to Heiko Tietze from comment #6)
> (In reply to Dieter from comment #4)
> > Result: Numbering of first column changes
> > Enhancement: Give possibility to number table per column
> 
> Something like Table > Properties > Text Flow: 
> 
> Numbering sequence: (o) Row ( ) Column

Yes, and it should become part of the table toolbar.
Comment 8 QA Administrators 2024-08-12 03:13:17 UTC
Dear Timur,

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