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

--- Comment #9 from Telesto <tele...@surfxs.nl> ---
Created attachment 180761
  --> https://bugs.documentfoundation.org/attachment.cgi?id=180761&action=edit
Example file Second attempt

(In reply to Michael Stahl (allotropia) from comment #8)
> i don't think there's an easy tweak to this that preserves the API
> compatibility that comment#4 is about, and it's a rather minor problem, you
> can always click on the image to delete it that way.

A small retry probably better describing the 'issue'. Primary question: What's
the value of anchoring an image to an character if the anchor is broken with
ease. The anchor suggests a connection between 'the character' and the image .
The image is positioned relative to the anchor point, so if the characters move
(drag/drop or copy/paste) the image should be following.

1. Open the attached file
2. Double click Lorem Ipsum
3. Drag the text to the top of the page (say it's a list without bullets)
4. Notice the image moving (why: image is anchored to character, and the anchor
is manually attached to 'm' of ipsum
5. CTRL+Z
6. Change the anchor of the image to 'to paragraph'
7. Change the anchor back to 'to character' (anchor will but after ipsum). Now
drag the text up again.. Image stay's behind (expected to move along with the
text) as in 4
8. Undo the dragging up (but anchor still behind 'ipsum')
9. Press CTRL+A and enable bulleted list
10. Move Ipsum Lorum up (with arrows). Notice the anchor moving along. 

I guess there being an explanation for each and every case in technical sense.
But from end-user perspective this kind of arbitrary.

And well 'to character' has to states. (A). Truly positioned to a character.
(B) put after a characters (most common, I guess). Which is not truly a to
character anchor, IMHO 

In case of 'to paragraph' we end up' what 'anchor to paragraph' means. Is the
image bound to the paragraph (the characters) or bound to paragraph location.

Currently it's mixture of both (case dependent) 

A fix would be to actually anchoring the anchor to a character and not the
'invisible' behind or in case of to paragraph 'prior' the visible character.
[sorry, for the bad terminology]. But I'm not overseeing the consequences..

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

Reply via email to