963939 - cursor appears and blinks in all areas of the webpage when i click using the mouse

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[sivasankar.p]

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131205075310

Comment 1

[dfern]

[bugday-20140127]
What are the detailed steps to reproduce?
Can you please give steps and specific pages?

Comment 2

[KORraN]

Same bug appeared for me in the latest beta. I often click on website and then scroll with cursors (up/down) but now it's impossible because only caret is moving through the content of website.

Comment 3

[dacr]

In FF 30 too. On any site.

Comment 4

[Brindusa Tot, DTE]

Could not reproduce this on Windows Vista x 64 bit with:
 - Firefox Release 43 - build ID 20160105164030, User Agent Mozilla/5.0 (Windows NT 6.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
 - Nigthly 46.0a1 - Build ID  20160107030235, User Agent  Mozilla/5.0 (Windows NT 6.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0

Can you please verify if this is reproducing on latest Firefox builds. If it still reproduces, could you please give specific steps and some pages where you encountered the bug.

Comment 5

[dacr]

(In reply to Brindusa Tot from comment #4)
> Could not reproduce this on Windows Vista x 64 bit with:
>  - Firefox Release 43 - build ID 20160105164030, User Agent Mozilla/5.0
> (Windows NT 6.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
>  - Nigthly 46.0a1 - Build ID  20160107030235, User Agent  Mozilla/5.0
> (Windows NT 6.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
> 
> Can you please verify if this is reproducing on latest Firefox builds. If it
> still reproduces, could you please give specific steps and some pages where
> you encountered the bug.

I no longer experience this error.

Comment 6

[Brindusa Tot, DTE]

Based on previous comment, mark the bug Resolve Worksforme.

Feel free to reopen it if the issue is back and reproducible.

Comment 7

[Brindusa Tot, DTE]

Remove the need info flag, as the issue is not reproducible on latest builds.

[e-mail], feel free to reopen it if the issue is back and reproducible.