When an image is anchored as 'As Character' it is not possible to drag it around like a character and drop it in a middle of a sentence. The only means of dragging an image set to 'As Character' is up and downwards, but it simply moves the image up and down according to the line its in, there isnt a means of moving it left and right or to the previous or next line. Version: 4.5.0.0.alpha0+ Build ID: e570cd7a293ceee175949dcc9656cdf776ae3c37 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-12-12_18:49:54 Tested it on Windows 7 and it acts the same.
Reproducible with LO 4.4.0.0.beta1 and 4.3.4.1 (Win 8.1). Text you can move everywhere you want by dragging it with the mouse. But an image anchored as character can only be moved up and down. But if you move it down then it becomes like an "enlarged" character (empty space above the image, -> try to put the cursor above the image -> a further bug).
The most optimal solution is that when an image is dragged with 'As Character', the image itself is not being dragged, but the anchor icon that appears and is draggable in 'To Character' gets dragged.
Scratch my last suggest, as the better thing is that to show the drag mouse icon, with the character dash showing where its new location will be, similar to how it shows this functionality when you highlight some text and drag it.
for the record a work around: Ctrl-X ... move ... Ctrl+V Ah well..
(In reply to Cor Nouws from comment #4) > for the record a work around: Ctrl-X ... move ... Ctrl+V > Ah well.. Yes i've had to use it a few times already. :D
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe OS: Windows 10 As of this version, character dragging still shows the unwanted behaviour. i.e. dragging an image anchored as character just moves it up and down within the line that it is in (ugh who would want this behaviour), and it is still not possible to drag it like a character and drop it in the middle of a sentence.
by design
I'm not sure what the explanation in bug 87720 comment 43 is supposed to mean related to this, but surely this isn't by design, there should be nothing preventing an object anchored "as character" to be repositioned. This has nothing to do whether the setting is the default or not, it's still a possible setting.
We discussed the topic in the design meeting. The default anchoring is To Character, by design, and those objects can be moved around. Not being able to drag an object when placed _As_ character makes sense consequently. As there is no other use case we better resolve the ticket as WF.
(In reply to Heiko Tietze from comment #11) > We discussed the topic in the design meeting. The default anchoring is To > Character, by design, and those objects can be moved around. Not being able > to drag an object when placed _As_ character makes sense consequently. As > there is no other use case we better resolve the ticket as WF. I feel like it must be pointed out: character selections can be dragged around. Not being able to drag an object that is anchored as character does not make sense, and is an annoyance UX-wise. As a bit of history wrt bug 87720, "as character" anchor being the default was introduced for interop reasons (primarily with Word), but later was abandoned due to this annoying bug. Documents containing images with "as character" anchor will continue existing, and this bug will continue being a bother regardless of what the default is. Please keep this bug report open.
Advantage is that you can use dragging (and keyboard) to change the positioning. Feel free to reopen, if you think dragging as character anchored object is needed.
Yes, thanks!
Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Changing this to enhancement because the design team said it is working as intended.