Closed
Bug 250117
Opened 20 years ago
Closed 20 years ago
Port fix for bug 20022 (:hover state not set) to Aviary branch
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: psellhorst, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040706 Firefox/0.9.0+ Recently, bug 20022 (:hover state not set until mouse move) has been fixed. The fix is available in recent Firefox trunk builds but not on the branch (I've checked this with both 2004-07-06 builds). Please consider porting the fix for bug 20022 to the Aviary branch in order not to have a Firefox 1.0 release with this annoying issue (latest duplicate: bug 248735) still present. This is also closely related to bug 50511 (~40 duplicates). Reproducible: Always Steps to Reproduce:
Reporter | ||
Comment 1•20 years ago
|
||
Setting blocking-aviary1.0? flag since having an incorrect mouse cursor while wheel-scrolling a page (which is a very frequent operation) falls into the "UI exhibiting sloppy behavior" category that's mentioned on blakeross.com.
Flags: blocking-aviary1.0?
Reporter | ||
Updated•20 years ago
|
Summary: Port fix for bug 20022 to Aviary branch → Port fix for bug 20022 (:hover state not set) to Aviary branch
Reporter | ||
Updated•20 years ago
|
Version: unspecified → 1.0 Branch
Comment 2•20 years ago
|
||
I'm not sure it does really fit into that category - this isn't a Firefox UI issue, it's a back-end issue. If all the stuff like this gets ported to Aviary for 1.0, we'll be waiting another 6 months for the 1.0 release. When Firefox returns to the trunk after 1.0, it will pick up all these back-end fixes anyway - then we get 1.0 sooner, and waste less time overall in porting stuff around...
Comment 3•20 years ago
|
||
See Bug 20022 comment #118. *** This bug has been marked as a duplicate of 20022 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.0?
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•