Created attachment 62585 [details] Video show bug Click on the border of a text frame. When the button is released, quickly move the mouse somewhere on the page. The frame follows the mouse and positions itself elsewhere. The expected behavior is that the frame stay in place. (cf attached video)
@Fabien Michel: Thank you very much for your report, especially for the attached videw, which is very impressive indeed! However, I can NOT reproduce the problem with LibreOffice 3.5.4.2 (Build-ID: 165a79a-7059095-e13bb37-fef39a4-9503d18), German langpack installed, on MacOS X 10.6.8 German UI. If I try to repeat exactly what the screencast shows, everything works for me as expected -- no moving frame, the frame stays in place. So we need to find out what makes the difference, i.e. why you see this problem and I don't see it. Therefore, I want to ask you: 1) Which version of MacOS X do you use (10.5.x, 10.6.x, 10.7.x)? 2) Do you have any kind of accessability utility enabled? I mean, in the MacOS System Preferences, in the section "Accès universel" (to quote the Frech titles, because Apple names this section very differently ;-), do you have checked any options, e.g. "Activer l’accès pour les périphériques d’aide"? Or do you have any other special system utilities installed? I ask this (no. 2) because the use of accessability utilities is know to cause many strange issues; the problem you observed could be one of these issues. 3) And I ask this also because the screencast shows very nice effects which emphasize the mouse pointer (cursor) by a yellow circle and emphasize every mouse click by a blue circle. Are these effects part of the screencast software, or are they added by some system utility you have installed? (Forgive me if no. 3 is a stupid question, but I just don't happen to know this ;-) And any special utility you may have installed could have an influence on the problem you observe. Thank you very much for your answers in advance!
Sorry for the lack of information. 1) I use MacOS 10.7.3 on a white macbook (2008) and LibreOffice 3.5.4.2 Build ID: 165a79a-7059095-e13bb37-fef39a4-9503d18 But i've also reproduce on a 10.6.x (macbook pro) With Libreoffice 3.5.3.x 2) I've try with and without accessibility option you describe. And it does not change anything. 3) I use http://www.screencast-o-matic.com/ to capture screen animation. It automatically add clicking and moving effects on the mouse. Of course the problem occur without this utility.
(In reply to comment #2) > Sorry for the lack of information. On the contrary, thank you very much for your additonal information and testing! It helps us to make sure that the issue is not related to some special circumstances (e.g., on MacOS X, accessibility options can cause really strange things in LibreOffice ...). And the one who has to say "sorry" is me ;-) After reading your answers, which made clear to me that there no special circumstances which could explain this issue, I tried again to reproduce your observation. And this time, it worked -- therefore: (Most times) REPRODUCIBLE with LibreOffice 3.5.4.2 (Build-ID: 165a79a-7059095-e13bb37-fef39a4-9503d18), German langpack installed, on MacOS X 10.6.8 German UI. Two observations: * for me, the frame just does not move always, but often; * I have to move the mouse really *very* quickly after I release the button to make the frame move. These two points may explain why I could not reproduce the problem when I tried first (comment #1) -- sorry again for that! -- I did not try hard enough and moved the mouse not quickly enough. Set Status to NEW because bug is reproducible. Set Version picker to "3.5.3 release" according to comment #2.
Also * REPRODUCIBLE with LibreOffice 3.4.4, German langpack installed, on MacOS X 10.6.8 German UI. Therefore changed Version picker to "3.4.4 release" (the Version field should always contain the FIRST version in which a bug can be reproduced). * REPRODUCIBLE with LibreOffice 3.6.0beta1 (Build ID: 1f1cdd8), German langpack installed, on MacOS X 10.6.8 German UI. So the bug is still present in the 3.6 branch. Can someone please test if this bug is reproducible on Windows/Linux? You may need to try more than once, of course (see my comment #3) ... Thanks!
(In reply to comment #4) > Can someone please test if this bug is reproducible on Windows/Linux? I did it myself for WinXP: REPRODUCIBLE with LibreOffice 3.5.4.2, German UI, on WinXP German UI. A real cross-platform bug. -> Changed Platform settings accordingly. @Thorsten Behrens, @Radek Doulik: Could you please take a look at this issue? It is not terrible, it is not very urgent, but it is still annoying and rather irritating. For example, if someone repeats this unintentionally two or three times, and each time moves a frame for some px, he/she will break the slide layout step by step and notice this only when it is too late, i.e. when Undo will not work anymore. Thank you very much in advance!
Always occurs with Version 3.6.3.2 (Build ID: 58f22d5) On Mac OS X Lion 10.7.5
** 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 (4.3.5 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) Thank you for your help! -- The LibreOffice QA Team
I can't reproduce this even if I try to move the mouse away as fast as humanely possible. Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+ Build ID: 07e84cae983c08afdba03018413a19d01abb3006 TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38
** 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.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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
** 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
Still occure with Version: 5.3.0.3 (Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1) On a recent MacBook Pro (2013, Core i5, SSD, 8Go RAM) on macOS El Capitan (10.11)
** 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 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
Dear fabien.michel, 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://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
Dear fabien.michel, 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
Took a look. Checked if I can simply reproduce, but not so simple - maybe my machine is too fast (?) That task is older and it would be interesting to hear on which system (regarding performance) this happens. @fabien.michel@hespul.org: Could you please add infos about system? Still - could *sometimes* get a move, but MouseUp & Move were so close together, I am not sure if that was indeed the error. What I tried is: Move mouse in a smooth regular movement to the right over the border, then - without changing movement - press & release left Mouse Button. Next I tried with & without snap-to-grid, no real change. Next I changed tools/options/impress/grid to much higher resolution -> THAT makes it immediately reproducible (!) Seems to have to do with minimal move/snap, will check code now. Note: Hard to debug, as always with interactions...
I'm now on a Linux based OS. Therefore the machine I'm working on is powerful. I can't reproduce the problem.
Indeed hard to debug. Not sure if that change of GridSnap is involved. I made sure that there is *no* direct call of SdrDragView::EndDragObj after SdrDragView::BegDragObj (so *without* SdrDragView::MovDragObj) except ckick without moving the mouse. Saw that at SdrDragView::BegDragObj param nMinMov (that defines on how many pixels it's a 'move' at all) gets set by FuSelection::MouseButtonDown where it gets calculated as sal_uInt16 nDrgLog = sal_uInt16 ( mpWindow->PixelToLogic(Size(DRGPIX,0)).Width() ); where DRGPIX is defined as const int DRGPIX = 2; // Drag MinMove in Pixel in sd/source/ui/animations/motionpathtag.cxx. Unfortunately not in configuration, but at just two pixels - and then snapping to position(s) if activated - that might already explain the 'effect'. It would be nice if the people seeing this problem could try with e.g. DRGPIX = 5 or 10 if it still happens. Two pixels might be too low for people with slow click or sensible optical mice or might even have to do with the nowadays usually highly increased ScreenResolution... If that is the case we should make that value configurable & evtl. 'scale' from a default value of '2' for 640x480 to the real screen resolution. Just my 2ct
I was able to reproduce the problem using xdotool on X11. The setup might not be exact - I am only able to reproduce it when LibreOffice Impress was out of focus to begin with. Steps: 1- Move window focus out of Impress. 2- Run `xdotool sleep 5 mousedown 1 mouseup 1 mousemove_relative 500 500`. 3- Hover mouse over the text frame border. 4- Wait for xdotool to complete.
Sarper Akdemir committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/83f7c6fe5bb233fa9827ff968710822b95562075 tdf#50725: sd: add new configuration option DragThresholdPixels It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Sarper Akdemir committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/4c0cda6831d2c401642d6b42c1f596cb68a1cece tdf#50725: sd: add new configuration option DragThresholdPixels It will be available in 7.6.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I have implemented Armin's suggestions as a fix for this one, hopefully this resolves problems mentioned. (i.e. bumping up the drag pixel threshold to 6 pixels & making it configurable)