Whenever you drag an paragraph-character-anchored object (or move it using arrow keys), its anchor moves together with the object. This makes it impossible to fine-tune position of objects on screen, when their anchors are set.
1. In a Writer document, add several paragraphs.
2. Insert an image, and anchor it to the first paragraph.
3. Now try to drag the image, with the goal to re-position it below, but not to change its anchor (assuming we want the image to be linked to the first paragraph's text, but be positioned somewhere at the bottom of the page).
=> The anchor moves to the following paragraphs when you drag, so the only way to make the desired change is to enter numbers into the Properties dialog.
Of course, the proposed method (bindable to some keyboard modifier like Ctrl+Alt+Shift) should limit the movement of the object to disallow making the object and the anchor on different pages.
I confirm the described situation with
Version: 188.8.131.52.alpha0+ (x64) / LibreOffice Community
Build ID: f96004096268f5e71120678e32fc8c74055819aa
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
but I think this is an enhancement request rather than a bug.
For me one general problem is, that LO has only very short informations about image anchoring  and we have a lot of report about it.
As commented on bug 141162 moving the object (or the anchor) with an accelerator key like alt being pressed would do the trick. Of course not available if anchoring is set to As Character.
Probably no need for further input from UX.
+1 for the feature as such.
However I'm pretty convinced that moving the image without the anchor snapping to a different location, will cause/uncover more layout-loops. Meta bug Anchor-and-Text-Wrap has some examples already IIRC
Image wrap + anchoring sec, and certainly in combo with cross paragraph text (say start paragraph on page 1, other part on page 2) is asking for problems, IMHO.
So this will be less fun for the developer(s) involved.. but well this is touching layout code, so not a big surprise, I guess..
(In reply to Telesto from comment #3)
> However ...
What is the added value of assumptions what would hypothetically *developers* would find and/or think (any layout loop bugs are something to fix, not to fear), especially when paired with careless reading skipping the bits specifically written in the issue description:
> Of course, the proposed method (bindable to some keyboard modifier like
> Ctrl+Alt+Shift) should limit the movement of the object to disallow making
> the object and the anchor on different pages.
The "combo with cross paragraph text (say start paragraph on page 1, other part on page 2)" is not "asking for problems", but a reasonable proposal tracked in bug 89082; but it's unrelated to this one.
(In reply to Mike Kaganski from comment #4)
> (In reply to Telesto from comment #3)
> > However ...
> What is the added value of assumptions what would hypothetically
> *developers* would find and/or think (any layout loop bugs are something to
> fix, not to fear),
You're are obviously right: layout bugs are something to be fixed and not to be feared. And yes, the added value of my remark low in quality..
It's more that this bug/ enhancement sounding "simple" to implement, but requiring quite a lot of expertise, experience, skill, stamina. [But yes, this doesn't need stating explicitly. And even if, I'm not qualified to do so...]
I do ask myself should this be implemented independently. The current anchoring/wrap framework which 'feels' [subjective, based on few bugs) prone to errors c.q. working with Band-aids. So improving this likely will expose more pre-existing problems.
> especially when paired with careless reading skipping the
> bits specifically written in the issue description:
> > Of course, the proposed method (bindable to some keyboard modifier like
> > Ctrl+Alt+Shift) should limit the movement of the object to disallow making
> > the object and the anchor on different pages.
Gotcha. However not only about moving the image, but you paragraphs/characters can move to, while editing.
> The "combo with cross paragraph text (say start paragraph on page 1, other
> part on page 2)" is not "asking for problems", but a reasonable proposal
> tracked in bug 89082; but it's unrelated to this one.
Sorry.. I didn't intend to say that this wouldn't be a reasonable proposal. More that this case can cause issues in specific consternations today
Anyhow: let's burry this as off-topic/noise. I will try to refrain from such comments in the future.