Closed
Bug 402992
Opened 17 years ago
Closed 17 years ago
Do not switch to a hand cursor on favicon hover
Categories
(Firefox :: Shell Integration, defect)
Firefox
Shell Integration
Tracking
()
VERIFIED
FIXED
People
(Reporter: faaborg, Assigned: Dolske)
References
Details
(Keywords: polish)
Attachments
(3 files, 1 obsolete file)
5.54 KB,
patch
|
Details | Diff | Splinter Review | |
3.15 KB,
patch
|
mconnor
:
review+
|
Details | Diff | Splinter Review |
1.19 KB,
patch
|
Details | Diff | Splinter Review |
Switching to the hand cursor on favicon hover (on both the location bar favicon and tab favicon) has the advantage of making the drag operation more discoverable. However, this is non standard behavior both in terms of fitting in with other applications on the OS, and in terms of normal use of the hand cursor. Additionally, changing the mouse cursor when the user happens to mouse over a favicon on their way to another target is slightly jarring. Favicon drags are not incredibly common, so the hand cursor is most likely to appear in situations where the user has no intention of interacting with the favicon.
While dragging favicons to the bookmarks toolbar is useful, it does not require increased discoverability at the cost of violating user interface guidelines and a minor increase of UI complexity.
Assignee | ||
Comment 1•17 years ago
|
||
Bug 372773 recently added this to the tab favicon, the url bar favicon has had this since at least mid 2004.
This is easy enough to undo (look for CSS "cursor: -moz-grab"), and Alex's argument is compelling, but since Beltzner ui-r+ the recent addition of this I'll wait for him to waffle. :)
Assignee: nobody → dolske
Blocks: 372773
Comment 3•17 years ago
|
||
We added it to the tabstrip to differentiate between a "this will drag the tab" action and a "this will drag the URI" action, but really, I think that's something which is better made evident by changing the cursor depending on the hover target of the drag, and even more really, I don't think I care to spend the effort to do that (though I'd take that patch!)
Anyway, ui-r. :)
Assignee | ||
Comment 4•17 years ago
|
||
I removed all the CSS rules for #wrapper-urlbar-container, because it seems that element ID doesn't exist any more (ie, the rules were already deadwood).
The only other usage of -moz-grab in the browser is in the window for customizing a toolbar, I didn't bother changing that since it seemed more sensible, and no one uses it anyway. :)
Attachment #289890 -
Flags: review?(mano)
Comment 5•17 years ago
|
||
Comment on attachment 289890 [details] [diff] [review]
Patch for review, v.1
r=mano code-removal-wise.
Attachment #289890 -
Flags: review?(mano) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #289890 -
Flags: approval1.9?
Comment 6•17 years ago
|
||
So, does beltzner's "ui-r" in Comment #3 above mean a minus? Sorry if that's normal usage, but it seems ambiguous. Once someone confirms that all reviews have been done, we'll approve.
Assignee | ||
Updated•17 years ago
|
Attachment #289890 -
Flags: ui-review?(beltzner)
Comment 7•17 years ago
|
||
Comment on attachment 289890 [details] [diff] [review]
Patch for review, v.1
I think this is good to go, beltzner's comment was a +, not a -, afaict.
Attachment #289890 -
Flags: ui-review?(beltzner)
Attachment #289890 -
Flags: ui-review+
Attachment #289890 -
Flags: approval1.9?
Attachment #289890 -
Flags: approval1.9+
Assignee | ||
Comment 8•17 years ago
|
||
Checking in browser/themes/gnomestripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/gnomestripe/browser/browser.css,v <-- browser.css
new revision: 1.141; previous revision: 1.140
done
Checking in browser/themes/pinstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/pinstripe/browser/browser.css,v <-- browser.css
new revision: 1.98; previous revision: 1.97
done
Checking in browser/themes/winstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/winstripe/browser/browser.css,v <-- browser.css
new revision: 1.138; previous revision: 1.137
done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 9•17 years ago
|
||
(In reply to comment #4)
> Created an attachment (id=289890) [details]
> Patch for review, v.1
>
> I removed all the CSS rules for #wrapper-urlbar-container, because it seems
> that element ID doesn't exist any more (ie, the rules were already deadwood).
#wrapper-urlbar-container exists when you customize the toolbar. The patch should be backed out.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•17 years ago
|
||
Attachment #289890 -
Attachment is obsolete: true
Assignee | ||
Comment 11•17 years ago
|
||
This fixes the regression Dao noted, by restoring the deleted rules. [There's a -moz-grab cursor in them, which is why I noticed them, but the usage there should be fine. I had deleted the rules because I thought they were just entirely unused.]
Attachment #291564 -
Flags: review?(dao)
Comment 12•17 years ago
|
||
Comment on attachment 291564 [details] [diff] [review]
Regression patch, v.1
r=mconnor
Attachment #291564 -
Flags: review?(dao) → review+
Assignee | ||
Comment 13•17 years ago
|
||
Checked in. Thanks for catching this so quick, Dao.
Checking in browser/themes/gnomestripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/gnomestripe/browser/browser.css,v <-- browser.css
new revision: 1.142; previous revision: 1.141
done
Checking in browser/themes/pinstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/pinstripe/browser/browser.css,v <-- browser.css
new revision: 1.99; previous revision: 1.98
done
Checking in browser/themes/winstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/winstripe/browser/browser.css,v <-- browser.css
new revision: 1.139; previous revision: 1.138
done
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Comment 14•17 years ago
|
||
verified fixed using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2pre) Gecko/2007120505 Minefield/3.0b2pre. I verified using the Mac nightly as well.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 15•17 years ago
|
||
I'm still seeing this with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008010604 Minefield/3.0b3pre
Assignee | ||
Comment 16•17 years ago
|
||
Are you using Proto? It still sets the cursor to the hand.
Reporter | ||
Comment 17•17 years ago
|
||
Yeah, I momentarily forgot that we haven't landed proto yet. Sorry about that.
Assignee | ||
Comment 18•17 years ago
|
||
Proto just landed, and regressed this.
Assignee | ||
Comment 19•17 years ago
|
||
Assignee | ||
Comment 20•17 years ago
|
||
Since this was the same change as was previously reviewed/approved, I went ahead and landed it.
Checking in browser/themes/pinstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/pinstripe/browser/browser.css,v <-- browser.css
new revision: 1.110; previous revision: 1.109
done
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Verified FIXED using:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4pre) Gecko/2008020423 Minefield/3.0b4pre
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008020419 Minefield/3.0b3pre
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008020423 Minefield/3.0b4pre
-and-
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008020419 Minefield/3.0b3pre
Status: RESOLVED → VERIFIED
Setting in-litmus? so that I remember to remove the hand-cursor verbiage from the testcase(s).
Flags: in-litmus?
You need to log in
before you can comment on or make changes to this bug.
Description
•