Created attachment 113477 [details] Illustration of over-sensitive target acquisition in LibreOffice Mac In LibreOffice 4.3.2.2 & Mac OSX 10.6.8, clicking a graphic to select it results in the graphic being moved, unless the mouse pointer is *perfectly still* over the graphic at the time of selection. The attached video illustrates what happens when shift-clicking to select multiple items, which inadvertently get dragged all over the screen together. This bug did not exist in earlier versions of LibreOffice Mac.
Stan: thanks for your bug report. It sounds nasty. Does upgrading to 4.4 improve matters in any way?
Unfortunately, official support of LibreOffice on OSX reaches end of life with the release of LO 4.4, so the only thing I can suggest is to try with the latest LO 436 version to see whether that changes anything, and if not, hope that the problem gets fixed accidentally by other changes to the code. I can't reproduce the problem on OSX 10.10.2 with master build 4500 alpha
(In reply to Alex Thurgood from comment #2) > Unfortunately, official support of LibreOffice on OSX reaches end of life > with the release of LO 4.4, so the only thing I can suggest is to try with > the latest LO 436 version to see whether that changes anything, and if not, > hope that the problem gets fixed accidentally by other changes to the code. > > I can't reproduce the problem on OSX 10.10.2 with master build 4500 alpha Libreoffice 4.3.x series will be the last series officially supported on OSX < 10.8
I confirm the same problem with the DRAW module using MacOS X 10.6.8. This problem existe since many years. I reproduce it simply by importing a big picture (2000x3000 pixels). Align it to the page. unselect it. Then click on the image : often it move by a few pixels. If not, unselect and select again faster.
*** Bug 89619 has been marked as a duplicate of this bug. ***
Confirmed via bug 89619
** 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.5 or 5.1.2 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-04-16
** 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.7 or 5.3.3 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-20170522
This is still present Version: 6.0.0.0.alpha1+ Build ID: 15dce20e8b97dbd0179f01910ca4d0027e80ff4e CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-20_06:46:46 Locale: en-US (en_US.UTF-8); Calc: group
I often accidentally move stuff around in Impress, too, in master builds. It is infuriating. This is very much still present.
... but of course, now when I *intentionally* try to "accidentally" move those "Click to add Title" or "Click to add Text" boxes, I can't... Can anybody reproduce it intentionally? Are you aware of what exactly you are doing when it happens? Or if not, can you try to explain how to intentionally get the effect (without actually clicking purposely on an object and dragging it).
This also happens to me all of the time with current releases of LO Draw, which is why for my work I now do nearly all of my drawing in LO41. It seems to me that the problem is much more noticeable when the object selection involves a relatively large object (in terms of occupied space on the sheet) which is overlapped or overlaid with a smaller object. For example, I can regularly reproduce this in Draw (as I hardly ever use Impress anyway) by pasting a bitmap image, and then tracing lines over the top of the image with the polygon tool to produce a vector silhouette / outline of the object in my bitmap). I would say that more than 50% of the time (subjective of course), the background object gets erroneously selected and moved before I've even had a chance to select the object I really want. YMMV.
Dear Stan Sporkistan, 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This seems to be still present Testing on the prioritizing flow chart :) https://wiki.documentfoundation.org/File:Prioritizing_Bugs_FlowChart.odg Version: 6.4.0.0.alpha0+ Build ID: 54028dc503fc08eb12e287919d5e2850cff05b73 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-07-31_01:48:19 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Dear Stan Sporkistan, 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
I can't replicate this on the flow chart, but it would be good if someone else tests as I'm not really using Draw / Impress Version: 25.2.1.2 (AARCH64) / LibreOffice Community Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 CPU threads: 10; OS: macOS 15.3.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
This is still reproducible for me in Draw with 25.2.1.2 My most common scenario is to insert an image that may either take up nearly all of the height or the width of a page. I then add numbering as textboxes and freehand curved lines, over the top of the image, or slightly outside of the image, to have the text box containing the number point to a specific part of the image. When selecting a textbox with the mouse, e.g. for editing, moving, or copying, it is fairly frequent for the underlying image to be captured and moved instead of the intended target. This requires repeatedly having to undo the erroneous move.