Using FizzillaMach/2003022103, the update of the cursor style based on CSS2 cursor properties on page elements incorrectly depends on the *focus* of those page elements If a cursor:pointer element has been clicked and has mouseover, cursor doesn't change on scroll. If a different, cursor:default element has been clicked and the cursor:pointer element has mouseover, cursor does change on scroll (the attached testcase demonstrates an apparent exception, however).

Also seing this on Windows 2000

I'm seeing something like this on all links: 1. Mouse over any link (cursor changes to 'hand') 2. Scroll the window (using scroll wheel or keyboard) so the cursor is no longer over a link. The cursor remains a 'hand' until it is moved (as soon as it moves at all, it returns to the proper state). The converse (?) is also true (when not on a link and scrolling so that the cursor does end up over a link).

*** Bug 200471 has been marked as a duplicate of this bug. ***

Bug 200471 (No image title tool tip when page scrolled instead of pointer moved) may be related, but it provides quite a different test case. Note that it uses only strict HTML 4.

Basically, this bug is about that when you scroll the page without moving the mouse, the cursor is not updated nor does the title or events trigger. This testcase is a table with 2 cells, the lower cell has a onmouseover attached to it, but doesnt trigger if you scroll with mouse wheel or arrow keys. The summary should be refrased to be more clearer

*** Bug 204848 has been marked as a duplicate of this bug. ***

What i said in comment about the events 6 is incorrect I guess? No other browser works like this.

isn't this another dup of bug 50511?

Isn't this bug and bug 50511 both dupes of: bug 20022 ":hover state not set until mouse move"

Adding: *". Image zoom in/out cursor update issue." to Summary. (see comment 7) *"Depends on: bug 20022", as bug 50511 does. (see comment 10) Changing: *Severity: Major -> Normal. (since both related bugs are 'Minor'...)

*** Bug 217914 has been marked as a duplicate of this bug. ***

*** Bug 212889 has been marked as a duplicate of this bug. ***

*** Bug 215912 has been marked as a duplicate of this bug. ***

*** Bug 205289 has been marked as a duplicate of this bug. ***

*** Bug 223400 has been marked as a duplicate of this bug. ***

*** Bug 227112 has been marked as a duplicate of this bug. ***

*** Bug 229218 has been marked as a duplicate of this bug. ***

*** Bug 230881 has been marked as a duplicate of this bug. ***

*** Bug 232390 has been marked as a duplicate of this bug. ***

Fixed with checkin of bug 20022 to trunk, 2004-02-03 16:11 -0800.

Bug 20022 backed out.

*** Bug 237263 has been marked as a duplicate of this bug. ***

*** Bug 245240 has been marked as a duplicate of this bug. ***

*** Bug 246502 has been marked as a duplicate of this bug. ***

Fixed by relanding of bug 20022.

(In reply to comment #26) > Fixed by relanding of bug 20022. !?!?!?!?!? I still can reproduce this with 0.9.1 !!! I think this bug should be re-opened!!!!

This checkin was on the trunk, not on the 1.7 or aviary branches. It will not go into Firefox 1.0

Please have a look at bug 252249. It looks like a similar bug still remains!

*** Bug 217111 has been marked as a duplicate of this bug. ***

*** Bug 261697 has been marked as a duplicate of this bug. ***

*** Bug 263836 has been marked as a duplicate of this bug. ***

*** Bug 264208 has been marked as a duplicate of this bug. ***

*** Bug 274615 has been marked as a duplicate of this bug. ***

*** Bug 214820 has been marked as a duplicate of this bug. ***

*** Bug 276591 has been marked as a duplicate of this bug. ***

*** Bug 277709 has been marked as a duplicate of this bug. ***

*** Bug 282430 has been marked as a duplicate of this bug. ***

*** Bug 250116 has been marked as a duplicate of this bug. ***