Summary: | Text copy-paste in tables (Draw) behaves strange | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Yan Pas <yanp.bugz> |
Component: | Draw | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | libreoffice-ux-advise, otavio |
Priority: | medium | Keywords: | needsUXEval |
Version: | 5.0.4.2 release | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 100366 | ||
Attachments: | Test case that confirms the bug |
Description
Yan Pas
2016-01-13 22:20:27 UTC
Created attachment 122006 [details]
Test case that confirms the bug
Bug confirmation
Bug confirmed on 5.0.4.2 and 5.1.0.2. Test case created on 5.1.0.2 is attached. You have to change the font for the whole table before pasting a cell text in order to see the bug. The font of the pasted text becomes liberation. It seems to work on 5.2. Please double check. LO master (5.3) reproducible. Once again: Insert table Type some text in 1st cell Select text, right click, Character.., change size and fonmt family Paste text to another cell -> FOrmatting lost (In reply to Yan Pas from comment #4) > LO master (5.3) reproducible. > Once again: > Insert table > Type some text in 1st cell > Select text, right click, Character.., change size and fonmt family > Paste text to another cell > -> FOrmatting lost Strange, works for me (Windows 5.2 and Linux 5.1), probably I missed something. What I do is: 1. Insert table in Draw 2. Enter text into first cell (123) 3. Set font size to 14 and bold 4. Copy text and paste it into cell A2 -> bold, 14 5. Use context menu > character to set font color to red 6. Copy and paste into A3 -> Red, 14, bold I don't know why, but I can't reproduce it now too (both on LO 5.0.5 and master) (In reply to Yan Pas from comment #6) > I don't know why, but I can't reproduce it now too (both on LO 5.0.5 and > master) Perhaps it's somehow related to styles, whether some property was set before or not. But anyway, let us close this bug. Feel free to reopen when the issue happens again. |