https://bugs.documentfoundation.org/show_bug.cgi?id=141747
Heiko Tietze <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Keywords|needsUXEval | CC| |heiko.tietze@documentfounda | |tion.org, | |[email protected] Status|UNCONFIRMED |NEW --- Comment #10 from Heiko Tietze <[email protected]> --- STR: * File > New to have a fresh start * Insert three page breaks * Go to page 2 and insert an image; add a caption so we have a numbered figure * On p1 add a cross ref to this figure showing the page number 1. cut the image (should be the same as delete) -> LO Writer empties the cross-reference; the field remains but one wouldn't know unless field shading is enabled -> MS Word keeps the number 2. paste on p3 -> LO Writer: the empty field remains empty -> MS Word: the reference still shows the previous page number + undo to get to the step after cut 3. Update fields -> LO Writer: nothing happens, meaning the empty field stays empty -> MS Word: the field text changes to a bold "Error! Bookmark not defined." If we could be smarter than MSO and update the field immediately after the target changes keeping some temporary link so the reference is updated properly after paste, it would be an advantage over competitors. Showing an "empty" field seems to be a bug. But I could imagine that this has been done intentionally for some reason. Maybe to avoid too many "Error: Bookmark missing" annotations in the document ;-). In fact, we should show such a text if the reference is dead-end. -- You are receiving this mail because: You are the assignee for the bug.
