firegestures
firegestures copied to clipboard
invalid mousedown state after switching tab with rocker gesture
Step to Reproduce:
- Rocker gesture (holding left button + press right button) to switch to the right tab.
- Release all buttons.
- Ctrl+Shift+Tab to switch to the left tab.
- Move the mouse pointer around.
Expected Results: Text should not be selected.
Actual Results: Text is selected without holding left button.
The same can sometimes be observed while closing a tab with LRL, I find the mouse selecting text even though I have not buttons pressed at the time.
I've also observed some kind of the "selected text" problem since I updated to Firefox 4. Perhaps this helps to find the problem:
Steps to reproduce:
- Open two tabs A and B and load web pages with text on it
- In tab A, change to tab B with rocker gesture (holding left button + press right button) with the mouse cursor being over some text (not link).
- Close tab B using close button on tab bar or close tab gesture.
- Observe text selection while moving the mouse cursor around.
Notice: The start of the selection is the position where you performed the rocker gesture in step 2! It is independent of the cursor position of the close tab gesture in step 3.
I have a similar, but not exactly the same, problem on Firefox 4 and 5:
Steps to reproduce it:
- open these pages in two adjacent tabs:
- http://www.xuldev.org/firegestures/changelog.php
- https://github.com/gomita/firegestures/issues/1
- make a gesture on page 1 that has no action assigned to it (just swirl it around in some circles)
- release right mouse button (the gesture line dissappears)
- switch tab (ctrl+tab) to page 2
- text on the page is now selected, as if the left mouse button was pressed. The selection changes as you move the mouse around
Such text selection happens roughly 20 times each workday for me. Very annoying. I hope there will be a solution for it soon. BTW are there any nightlies of Firegestures for direct installation?
I should add that the problem does not show up on all pages. I'm not sure why it happens on only some pages. Could it be related to how the page uses javascript?