Closed
Bug 853447
Opened 12 years ago
Closed 7 years ago
Adding some type of Tab indication when hovering mouse over
Categories
(Firefox for Metro Graveyard :: App Bar, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: kjozwiak, Unassigned)
References
Details
(Whiteboard: [feature] p=0)
I think it would be a good idea if we added some type of border or graphic indication to let the user know what tab window the cursor is currently hovering over. This would make it a lot more intuitive to the end user.
Actual Results:
- Hovering over tab windows doesn't do anything
Expected Results:
- Some type of indication or border when a mouse hovers over the tab
Updated•12 years ago
|
Whiteboard: p=1
Comment 1•12 years ago
|
||
Even on Desktop firefox when you move your mouse over tabs there is a slight change in the look of the tab. If it was a simple background border color change or something like that it would be trivial to implement.
Flags: needinfo?(ywang)
Keywords: uiwanted
Updated•12 years ago
|
Summary: adding some type of Tab indication when hovering mouse over → Change - Adding some type of Tab indication when hovering mouse over
Whiteboard: p=1 → feature=change c=tbd u=tbd p=1
Updated•12 years ago
|
Whiteboard: feature=change c=tbd u=tbd p=1
Updated•12 years ago
|
Updated•11 years ago
|
Blocks: metrobacklog
Updated•11 years ago
|
No longer blocks: metrov2defect&change
Updated•11 years ago
|
Whiteboard: [v1?]
Updated•11 years ago
|
Summary: Change - Adding some type of Tab indication when hovering mouse over → Adding some type of Tab indication when hovering mouse over
Whiteboard: [v1?] → [feature] p=0
Comment 4•11 years ago
|
||
Removing 'uiwanted' keyword as UX dependency bug has been created which blocks bug 853447.
Keywords: uiwanted
Assignee | ||
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
Comment 5•7 years ago
|
||
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•