Closed
Bug 664251
Opened 15 years ago
Closed 15 years ago
Don't use the Firefox icon in the add-on developer hub header
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect, P5)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
VERIFIED
FIXED
6.1.3
People
(Reporter: krupa.mozbugs, Assigned: gkoberger)
References
()
Details
Attachments
(2 files)
steps to reproduce:
1. Load https://addons-next.allizom.org/z/en-us/developers/
2. Notice the header
expected behavior:
Since developer hub is not app-specific, we shouldn't be using the Firefox logo in the header.
observed behavior:
We use the firefox logo in the header. See screenshot.
Comment 1•15 years ago
|
||
I think we may have decided to do that on purpose here. Chowse may know.
Assignee: nobody → chowse
Target Milestone: 6.1.1 → 6.1.2
Comment 2•15 years ago
|
||
No, Krupa's right. I discussed this with Fligtar offline and we shouldn't be using the Firefox logo for the dev hub, even if it is largely Firefox-focused.
There are two solutions we were considering:
1. Replace the logo with something more appropriate, like the puzzle piece
(to imply 'add-on') or the spaceship. My leaning was toward the former (once
I could find get my hands on a large puzzle piece icon), but Fligtar
indicated that we are moving away from the puzzle piece motif.
2. Eliminate the logo and bring back the previous style of page header: "Add-on"
in smaller type on one line, and "Developer Hub" in larger type on the
next line. I'm okay with this, but I don't think this works as well now
that there's a menu beneath the heading.
For now, it might be better to go with (2), since I'm still lacking a large puzzle piece icon in addition to the branding question.
Updated•15 years ago
|
Assignee: chowse → gkoberger
Priority: -- → P5
Target Milestone: 6.1.2 → 6.1.3
| Assignee | ||
Comment 3•15 years ago
|
||
Chowse: I went with 1, merely because I had the icon and after testing both, I thought it looked less plain than option 2.
That being said, I'm 100% fine with you reopening this bug with a quick mockup of how #2 (with "Add-on" on it's own line) should look.
http://github.com/jbalogh/zamboni/commit/4581055
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 4•15 years ago
|
||
Please see my email from Monday about this:
"The only issue I see is that we're using an older design of the header -- the latest one from bug 654064 is http://www.cl.ly/3G3K321w2R321J200B2P . Currently the header reads as "Firefox Developer Hub" and isn't related to add-ons. When putting this back, please make sure to use the same markup as we did previously as the "Add-on" and "Developer Hub" sections were specially tagged for localization."
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 5•15 years ago
|
||
That was a wordy email. I may have skimmed.
Anyway, fixed: http://cl.ly/1A2N0b3r0h3v162W2s1z
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 6•15 years ago
|
||
verified fixed at https://addons.allizom.org/en-US/developers/
Status: RESOLVED → VERIFIED
| Reporter | ||
Comment 7•15 years ago
|
||
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•