On Sun, Dec 14, 2008 at 07:39:10PM -0800, <email address hidden> wrote:
> 1. In Firefox, sometimes moving the mouse over a link only changes the cursor
> for the fraction of a second in which the cursor is actually moving. When the
> cursor is not moving and it's on a link, it just uses the normal cursor image.
> This doesn't always happen, and I don't know what triggers it.
verified, reproducable. running firefox through xmond reveals that it's
usually some order of:
<- MotionEvent [event=0xABCD]
-> ChangeWindowAttributes [link cursor]
-> TranslateCoordinates [0xABCD, 0, 0]
some more of the TC request, then some create pixmap/copy area/free pixmap
-> ChangeWindowAttributes [normal cursor]
-> TranslateCoordinates [0xABCD, 0, 0]
I have no idea why or what that is supposed to do. First one to bisect wins.
On Sun, Dec 14, 2008 at 07:39:10PM -0800, <email address hidden> wrote:
> 1. In Firefox, sometimes moving the mouse over a link only changes the cursor
> for the fraction of a second in which the cursor is actually moving. When the
> cursor is not moving and it's on a link, it just uses the normal cursor image.
> This doesn't always happen, and I don't know what triggers it.
verified, reproducable. running firefox through xmond reveals that it's
usually some order of:
<- MotionEvent [event=0xABCD] ributes [link cursor] nates [0xABCD, 0, 0] ributes [normal cursor] nates [0xABCD, 0, 0]
-> ChangeWindowAtt
-> TranslateCoordi
some more of the TC request, then some create pixmap/copy area/free pixmap
-> ChangeWindowAtt
-> TranslateCoordi
I have no idea why or what that is supposed to do. First one to bisect wins.