Closed
Bug 868622
Opened 11 years ago
Closed 10 years ago
[UX] Implement the new Australis styling for the refresh/stop/go buttons
Categories
(Firefox :: Theme, defect)
Tracking
()
People
(Reporter: rexyrexy2, Assigned: mmaslaney)
References
Details
(Whiteboard: [Australis:M-] [ux])
Attachments
(3 files, 2 obsolete files)
In the UX builds, the refresh/go/stop buttons still have the old non-australis styling. The new styling should be implemented.
Should block bug 727650.
Blocks: australis-buttons
Blocks: australis-navbar
Updated•11 years ago
|
Whiteboard: [Australis:M?]
The australis has stop, go, and refresh buttons that have a background on hover and press. this should be implemented
Flags: needinfo?(shorlander)
You shouldn't have reset the flag. FWIW see bottom : http://people.mozilla.com/~shorlander/files/australis-designSpecs/australis-designSpecs-windows7-mainWindow.html
Updated•11 years ago
|
Flags: needinfo?(shorlander)
Comment 5•11 years ago
|
||
Moving to Australis v2
Flags: needinfo?(shorlander)
Whiteboard: [Australis:M?] → [Australis:M-]
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•11 years ago
|
Whiteboard: [Australis:M-] → [Australis:M-][Australis:P?]
Updated•11 years ago
|
Whiteboard: [Australis:M-][Australis:P?] → [Australis:M-]
Updated•10 years ago
|
Flags: firefox-backlog?
Updated•10 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Updated•10 years ago
|
Whiteboard: [Australis:M-] → [Australis:M-] p=0 [qa?]
Updated•10 years ago
|
Summary: Implement the new Australis styling for the refresh/stop/go buttons → [UX] Implement the new Australis styling for the refresh/stop/go buttons
Whiteboard: [Australis:M-] p=0 [qa?] → [Australis:M-] [ux] p=0 [qa-]
Comment 6•10 years ago
|
||
The spec doesn't consider the dropdown arrow in the awesomebar. I think that's the only detail we need to figure out before this can move to implementation.
Updated•10 years ago
|
Assignee: nobody → mmaslaney
Status: NEW → ASSIGNED
Whiteboard: [Australis:M-] [ux] p=0 [qa-] → [Australis:M-] [ux] p=2 s=33.1 [qa-]
Updated•10 years ago
|
Iteration: --- → 33.2
Points: --- → 2
QA Whiteboard: [qa-]
Whiteboard: [Australis:M-] [ux] p=2 s=33.1 [qa-] → [Australis:M-] [ux]
Updated•10 years ago
|
Iteration: 33.2 → 33.3
Assignee | ||
Comment 7•10 years ago
|
||
Mock
Assignee | ||
Comment 8•10 years ago
|
||
Spec
Assignee | ||
Comment 10•10 years ago
|
||
Assets
Comment 11•10 years ago
|
||
(In reply to Philipp Sackl [:phlsa] from comment #6) > The spec doesn't consider the dropdown arrow in the awesomebar. I think > that's the only detail we need to figure out before this can move to > implementation. This is still needed.
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 12•10 years ago
|
||
(In reply to Guillaume C. [:ge3k0s] from comment #11) > (In reply to Philipp Sackl [:phlsa] from comment #6) > > The spec doesn't consider the dropdown arrow in the awesomebar. I think > > that's the only detail we need to figure out before this can move to > > implementation. > > This is still needed. Having a similar style on the dropdown arrow would look odd (floating box in the middle of the URL bar), so we should stay with the current hover/active style on that.
Comment 13•10 years ago
|
||
The mockups only shows hover and active states. They don't show the default state. I assume that state would continue to have no border and no background. How is the spacing around the dropdown arrow and the reload icon supposed to work out there? It seems like they might be too far apart.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•10 years ago
|
No longer blocks: australis-buttons
Comment 14•10 years ago
|
||
Please no. The red background snatches away the user focus; it's glaring to the eyes. A red background was proposed a few years ago, and was shot down again and again for the exact same reason. Nothing else in the browser is glaring red. It doesn't fit and hurts usability.
Comment 15•10 years ago
|
||
(In reply to henryfhchan from comment #14) > Please no. The red background snatches away the user focus; it's glaring to > the eyes. A red background was proposed a few years ago, and was shot down > again and again for the exact same reason. Nothing else in the browser is > glaring red. It doesn't fit and hurts usability. The background is only red on hover, so it won't grab attention unless the user is already focusing on this part of the UI.
Comment 16•10 years ago
|
||
(In reply to Philipp Sackl [:phlsa] from comment #12) > (In reply to Guillaume C. [:ge3k0s] from comment #11) > > (In reply to Philipp Sackl [:phlsa] from comment #6) > > > The spec doesn't consider the dropdown arrow in the awesomebar. I think > > > that's the only detail we need to figure out before this can move to > > > implementation. > > > > This is still needed. > > Having a similar style on the dropdown arrow would look odd (floating box in > the middle of the URL bar), so we should stay with the current hover/active > style on that. It's correct, but I was thinking about the icon which is different on the spec compared to what is currently used (at least on Windows).
Assignee | ||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 18•10 years ago
|
||
There isn't Any other button that changes so abruptly on hover (especially) or pressed state. This seems very inconsistent with other elements in Australis.
Assignee | ||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → Firefox 33
Comment 19•9 years ago
|
||
Why can't this land?
Comment 20•9 years ago
|
||
(In reply to Gary [:streetwolf] from comment #19) > Why can't this land? Because this is a UX bug - all that's been done is design work. Implementation is bug 1040804, and nobody has written a patch.
Comment 21•9 years ago
|
||
Thanks for the info.
You need to log in
before you can comment on or make changes to this bug.
Description
•