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

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=11
                   |                            |8729,
                   |                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=11
                   |                            |2569
           Hardware|x86 (IA32)                  |All
             Blocks|                            |87740
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org

--- Comment #23 from Stéphane Guillou (stragu) 
<[email protected]> ---
Related problem that definitely is a bug is: PDF export and print (preview too)
look different to what's on screen when editing.
- Following steps in comment 4, export/print have a larger row height to
accommodate the overflowing wrapped text;
- in some other cases, the overflowing text overlaps onto the next row in the
export/print. See bug 112569 and its "see also"s.

Another issue: if a cell has such a "wrapped text overflow", the row height
does update when applying e.g. a border to the cell. Surely we can't justify
not updating the row height on resizing a column, but updating it when applying
a border...

But all these issues need breaking into precise reports with simplest steps, if
not already reported. The more I test this area, the more I see inconsistencies
between canvas and export/print, and use of the overflow indicator, depending
on steps and their order.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=87740
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to