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

--- Comment #11 from Telesto <[email protected]> ---
Created attachment 178010
  --> https://bugs.documentfoundation.org/attachment.cgi?id=178010&action=edit
Example file (for from scratch

Updated steps the create the file in question
1. Open the attached file
2. Select the left image (notice anchor position)
3. Press arrow down until bottom (there is empty new paragraph)
4. press Arrow up to move it the original position
5. Press Enter above the paragraphs, until split is expected


(In reply to Dieter from comment #10)
> Since first image ist anchored to a character in the last line, for me it's
> the expected result, that at least image moves to next page. So perhaps the
> bug is not text flow, but that anchor is still in last line after step 4 of
> creating the file. But actually I can't reproduce this behaviour. If I move
> image with arrow key, anchor doesn't move.
> 

The behaviour is technically correct. However from user perspective quite hard
to grasp. And well there is also a different case bug 147155 which likely
caused by the same behaviour.

The single paragraph moving across a page with images anchored to it (to
character) where the anchor is put at certain spot, is source of trouble. (page
loops, refusing movement etc)

The major problem is where to which character the 'to character' anchor snaps
too if it's done automatically... 

Sometimes I think the anchor should always be in the neighbourhood of the
image.. So LibreOffice should auto-adjust the anchor, if the distance between
anchor & image being to width

Obviously limiting the ability to being able to set the to character anchor
manually

Alternative would be to anchor a to character anchor to start of the paragraph
(top left corner of the paragraph) (so exactly as 'to paragraph' anchoring, by
default). With only an exception made in case someone manually dragging the
anchor to different spot.

This would trim down the risk of having anchors at undesired locations

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

Reply via email to