Closed
Bug 496795
Opened 16 years ago
Closed 16 years ago
Add-on Listing Page: UI
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect)
addons.mozilla.org Graveyard
Public Pages
Tracking
(Not tracked)
VERIFIED
FIXED
5.0.7
People
(Reporter: mikelee, Assigned: andrew)
References
()
Details
(Whiteboard: [webmocha])
As indicated on the Tagging Spec
(http://docs.google.com/Doc?docid=dds6vwb4_1dxwx5vg3&hl=en)
1.9 - Add-on listing page
Tags will appear on the add-on listing page as a cloud sorted alphabetically. The size and emphasis of the tag should represent its popularity in the system. Clicking on a tag will take you to one of the tag pages.
This bug involves the HTML/CSS/jQuery portion of this task.
Updated•16 years ago
|
Whiteboard: [webmocha]
We discussed this in an email thread, but to keep all relevant info here, I'm posting this additional info.
Here is what the current Add-on Listing Page looks like (currently live):
https://addons.mozilla.org/en-US/firefox/addon/60
Here is what the Add-on Listing Page should look like:
http://people.mozilla.com/~jscott/bandwagon/clearleft/v11/Add-on-view-With_Contributions.png
http://people.mozilla.com/~jscott/bandwagon/clearleft/v11/Add-on-view-Without_Contributions_Share.png
Andrew, you only need to build the tagging pieces in the right sidebar. If you want to build more of it, I'm sure Jeff Balogh wouldn't mind ;-) But that would be a secondary priority to the other tasks. You can follow along on Jeff's work on the Add-on Listing Page here:
https://bugzilla.mozilla.org/show_bug.cgi?id=496662
Some of the icons you'll need in the right column can be found here in SVN:
/site/app/webroot/img/amo2009/icons/icons.png
The "x" next to each tag only shows up upon hover of the tag itself.
Hi Neil,
We have a question. In this wireframe:
https://bug488517.bugzilla.mozilla.org/attachment.cgi?id=380326
There is a system message at the top that says, 'You deleted the tag "tag name". Undo?' Is there an existing style for such system messages? If so, do you know where we can find it?
Comment 3•16 years ago
|
||
Hi Mike -
There isn't a style for this yet as it's new. It's basically the first of what I'm hoping will be many instances where we implement undo rather than warnings.
Comment 4•16 years ago
|
||
Sorry, hit commit too quickly :) - I can mock up a design for this if you like.
Undo is a piece of cool functionality. Perhaps we could follow Gmail's model and basically wait a few seconds before committing the change. Or would you guys prefer another behavior?
And we'd love a quick design mock for this Neil, just to make sure we implement a design you guys like :) Thanks!
| Assignee | ||
Comment 6•16 years ago
|
||
well, Undo is really just "add it again" so it doesn't need to wait, esp if you browse away from that page before your remove "took place".
Comment 7•16 years ago
|
||
(In reply to comment #2)
> Hi Neil,
>
> We have a question. In this wireframe:
> https://bug488517.bugzilla.mozilla.org/attachment.cgi?id=380326
>
> There is a system message at the top that says, 'You deleted the tag "tag
> name". Undo?' Is there an existing style for such system messages? If so, do
> you know where we can find it?
We have a notification element in views/elements/notification.thtml
Comment 8•16 years ago
|
||
We talked about this in the meeting today. If we can make the deleted message just down by the tag element that would be better, especially if someone has scrolled down the page a bit. That means we wouldn't use the Notification element here since it's too giant. Maybe wenzel could create a mini class for the notification element that we could use in constricted spaces? hmm? :)
| Assignee | ||
Comment 9•16 years ago
|
||
Fixed, ready for qa r28193
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Verified FIXED on https://preview.addons.mozilla.org/en-US/firefox/addon/4999 and others; we've (Krupa, Raymond, mostly) been testing and filing bugs as we go along.
Status: RESOLVED → VERIFIED
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
•