https://bugs.documentfoundation.org/show_bug.cgi?id=173944

            Bug ID: 173944
           Summary: FILEOPEN RTF: tables inside shapes lose containing
                    table rows or prevent import
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: macOS (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Description:
A table cell can contain a shape whose text has its own table. Importing that
structure can remove the containing table's second row, and a shape inside a
nested parent table can prevent the file from loading. The attached examples
use explicit row definitions; reproducing them does not require the inherited
row-definition omission in TDF#173698's original report.

Steps to Reproduce:
1. Use LibreOffice
2. Open the attached shape-table-parent-row.rtf in Writer.
3. Inspect the containing table's row and column count and the tables inside
the two shapes.

Actual Results:
The containing table has one row instead of two.

Expected Results:
The containing table has two rows, three columns, and six cells. The first row
is A1 / B1 / C1. The second row contains PrefixMiddleSuffix / B2 / C2, with
both shapes anchored in A2. One shape contains the two-cell A / B table, and
the other contains the one-cell X table; each child belongs to its own shape.


Reproducible: Always


User Profile Reset: No

Additional Info:
Second example: import failure

Open shape-table-nested-parent.rtf.

Writer fails to load it: the CppUnit importer receives no document component.
Expected: the containing table has two rows and two columns, its second row
contains a nested cell with a shape, and the shape's own table has two rows and
two columns. The sentinel Outer B2 sentinel and shape Child A2 / Child B2
remain intact; Child trailing remains inside the shape story.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to