Closed Bug 1257854 Opened 4 years ago Closed 3 years ago
Pointer freezes on wrong position for the recipient (both host and guest) if cursor is moved a little faster
[Affected versions]: - Firefox 45.0.1 (with hello version 1.1.14) - Firefox 46 beta 2 (with hello version 1.1.12) - Latest Developer Edition (hello version 1.2) - Latest Nightly (hello version 1.2) [Affected platforms]: - Ubuntu 14.04 32-bit - Mac OS X 10.11.1 - Windows 10 64-bit - Windows 7 64-bit [Steps to reproduce]: 1. Start Firefox 2. Start a conversation between two PC's or two browsers 3. Move the cursor to a point and then move it from one faster movement to a different point. (happens on both guest or host side) [Expected result]: - Cursor follows the start and end point of the movement [Actual result]: - Cursor fails to follow the whole movement from one stroke [Regression range]: - This is not a regression range, it was introduced along with the implementation of sharing pointers. - If I install older versions of the add-on on Nightly, hello will be broken so I’m unable to provide a regression through add-on versions. (I could install 0.2 though but pointers were not enabled there) [Additional notes]: - Screencast showing the issue attached. - Pointer will jump to the end point of the movement if cursor is moved again.
I'm assuming this is because of the debouncing: https://github.com/mozilla/loop/blob/master/add-on/chrome/bootstrap.js#L839 It'll grab the first movement and ignore others for 100ms. The final cursor position is probably more important than some intermediate one that happened to be caught after the 100ms timeout. I'm not sure how many users will quickly move the cursor exactly to some spot and stop vs slowing down at the target.
Priority: -- → P2
Whiteboard: [triage] → [btpp-fix-later]
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.