Bug 74346 - EDITING: Drag&drop within document: drop-location marker is laggy, sometimes unresponsive
Summary: EDITING: Drag&drop within document: drop-location marker is laggy, sometimes ...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2014-02-02 00:48 UTC by dg1727
Modified: 2015-12-15 11:03 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dg1727 2014-02-02 00:48:55 UTC
1.  Create a new document in LO Writer.  
2.  Type a sentence.  (I wrote one that was a little more than one line long.)  Press ENTER at the end to make the sentence into a paragraph.  I did this twice to leave a blank line between paragraphs.  
3.  Use copy-and-paste to duplicate the paragraph a couple of times.  
4.  Using the mouse, select (highlight) a word.  
5.  Try to drag-and-drop the selected text to somewhere else in the same document.  Keep the left mouse button held down while you move the mouse around to various candidate drop locations.  There is normally a vertical checkered bar, like a text cursor but checkered, that previews where the dragged text would be dropped if you were to release the mouse button.  

Issue:  This checkered vertical bar has too much lag in following the mouse.  Sometimes it doesn't move at all to a given position between 2 characters until the user has tried a dozen times or more.  

This appears to be a regression.  I don't remember the last version of LO I used that didn't have this issue, though.  

LibreOffice 4.1.4.2 on Ubuntu 13.04.  I'm using the "libreoffice/ppa" PPA from launchpad.net.
Comment 1 Yousuf Philips (jay) (retired) 2014-07-07 07:04:10 UTC
Dear dg1727,

I can confirm this is there in 4.1.6, 4.2.5 and 4.3.0 on Linux Mint. It is a regression as it doesnt happen in 4.0.6, and the delay time for the cursor to move to its new location maybe just half a second.
Comment 2 Yousuf Philips (jay) (retired) 2014-07-07 15:17:21 UTC
This behaviour only seems to happen when following the steps provided, as the regular drag and drop in other files dont show this issue.
Comment 3 Joel Madero 2014-07-16 04:47:53 UTC
Prioritizing:
Minor - can slow down professional quality work but won't prevent it
Medium - default is low, bumped up because of regression

 85835eaea0e00bbe3138486781a507e436bc9263 is the first bad commit
commit 85835eaea0e00bbe3138486781a507e436bc9263
Author: Bjoern Michaelsen <bjoern.michaelsen@canonical.com>
Date:   Wed Oct 16 04:09:52 2013 +0000

    source-hash-6978ddbf4738b4c53b9d2edbe6d5ad6a061d0d0f
    
    commit 6978ddbf4738b4c53b9d2edbe6d5ad6a061d0d0f
    Author:     Julien Nabet <serval2412@yahoo.fr>
    AuthorDate: Sun Jan 20 22:05:44 2013 +0100
    Commit:     Julien Nabet <serval2412@yahoo.fr>
    CommitDate: Sun Jan 20 22:05:44 2013 +0100
    
        Typo
    
        Change-Id: I94fb3020057fb1fb370ffdffee82e40da44bf35b

:100644 100644 079ecf5df05da7eab985569292d3a97a92ba1916 e0fb278a62f74246d4e7e854edda75a50c5d8910 M	ccache.log
:100644 100644 72ecc6495bfd8eaccc75f8f1b2d971b788ef9fae defa53e2eb21f85369551cb7bd33a41411af7206 M	commitmsg
:100644 100644 adf69b8185615a4bc0d40db9df58f3fc035cd75b 92cecd1d285b4493c39b38e636f7b560f40eb5ed M	dev-install.log
:100644 100644 151d6a303331592a750839208a71e26aaca46353 df30eda7f3b88b3394c69c749e2460d95f41fa55 M	make.log
:040000 040000 afe902852cd6d046ee88fa874b8759063365aba1 21a7f395a23b3d284ea834b61bd8935a85d48b99 M	opt


# bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
# good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932
git bisect start 'latest' 'oldest'
# bad: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect bad e02439a3d6297a1f5334fa558ddec5ef4212c574
# good: [8f4aeaad2f65d656328a451154142bb82efa4327] source-hash-1885266f274575327cdeee9852945a3e91f32f15
git bisect good 8f4aeaad2f65d656328a451154142bb82efa4327
# good: [9995fae0d8a24ce31bcb5e9cd0459b69cfbf7a02] source-hash-8600bc24bbc9029e92bea6102bff2921bc10b33e
git bisect good 9995fae0d8a24ce31bcb5e9cd0459b69cfbf7a02
# bad: [8ad82bc1416a07501651e8d96fe268e47d3931d3] source-hash-13821254f88d2c5488fba9fe6393dcf4ae810db4
git bisect bad 8ad82bc1416a07501651e8d96fe268e47d3931d3
# bad: [238338bc4111eb82429ea47384d4012bcd7cdc3e] source-hash-b6ba04639b9922f6717f79ac4be215e09691d7a9
git bisect bad 238338bc4111eb82429ea47384d4012bcd7cdc3e
# bad: [89dc8a802d1625e0efd88ba0fb720b22be87f3f0] source-hash-da03bb1ee6a69d2f4fef4c3ca0adc0ba9588bd19
git bisect bad 89dc8a802d1625e0efd88ba0fb720b22be87f3f0
# bad: [fe956dc63cc7ed1831f0e7e9e7253ea4d8c99549] source-hash-b15f095293c6127ecaef2f0fa3a1683e72392835
git bisect bad fe956dc63cc7ed1831f0e7e9e7253ea4d8c99549
# bad: [cd762eb968ba8783f726b67d9d70b0a76f4eb55d] source-hash-c9562064740baed3a9978723c5fe77b44a13a7aa
git bisect bad cd762eb968ba8783f726b67d9d70b0a76f4eb55d
# bad: [85835eaea0e00bbe3138486781a507e436bc9263] source-hash-6978ddbf4738b4c53b9d2edbe6d5ad6a061d0d0f
git bisect bad 85835eaea0e00bbe3138486781a507e436bc9263
# first bad commit: [85835eaea0e00bbe3138486781a507e436bc9263] source-hash-6978ddbf4738b4c53b9d2edbe6d5ad6a061d0d0f
Comment 4 Matthew Francis 2015-01-20 03:04:10 UTC
I got a different bibisect result from this - to be taken with a pinch of salt, the bug may not be as reproducible as it seems

# first bad commit: [5b352a8b3b7a2225e56a9143b5c0046f8eeb4a52] source-hash-3c70c8e449253b4219c12ee4ef50384030a474ef
Comment 5 Matthew Francis 2015-01-20 03:16:05 UTC
Probably the below commit (again) - there was a recent commit on master relating to this under bug 73165, and indeed when I check, this bug seems resolved on master now

Setting RESOLVED - WORKSFORME


commit 7a5272dc29c6efdaa99f97a627e6d9b695ae32f6
Author: pkoroau pkoroau <pkoroau@gmail.com>
Date:   Thu Dec 20 12:18:57 2012 +0100

    fdo#38837: Timers must end eventually [Writer idle timer]
    
    Change-Id: I36c6c56d7277b9b3853b846c86c1f4dd47ebdb08
    Signed-off-by: Luboš Luňák <l.lunak@suse.cz>
Comment 6 Robinson Tryon (qubit) 2015-12-15 11:03:18 UTC
Migrating Whiteboard tags to Keywords: (bibisected)
[NinjaEdit]