There are various issues with the current Downloads Panel design: - not enough downloads shown - no speed - order of downloads - small actionable icons I'm sure I've seen a mock-up of a redesign of the panel made by shorlander that was exactly addressing these issues. Regardless, we should improve the current design to satisfy more use-cases.
Here's a downloads panel mock-up that shorlander was at least fiddling with: http://people.mozilla.org/~shorlander/mockups-interactive/australis-interactive-mockups/windows8.html
I might be able to work on this in a week (only Linux theming, though). Not yet assigning it to myself, will do so later. The mockups look pretty nice :)
I'd also like to work on this, but I think it'd be good to allow Stephen to ping us when he thinks the design/ mockup is done and ready for implementation. Since there's quite a bit of text shown in the mockup, I'd like to discuss the technical implications of that wrt l10n, for example.
Whiteboard: [tracking] → [tracking] [Australis:P3-]
A couple of minor tweaks to the mockups: - Should those vertical separators span the entire height of the item? On hover the length of the separator does this, which might look strange. - The 1022/1023 probably should have a unit somewhere - What does the "show info" thing do (in detail)? Right now, a deleted download has no actions that can be taken. It also is devoid of feedback on the lack of the file (the item just sites there inert), but I'm not sure if we have a view for info on deleted downloads, or if we need one. If we don't have one but do need one, a mockup would be nice :)
I really don't think we should prioritize this until we have mockups ready and are sure it's actually more important than the myriad of P4/P5 issues we still have.
Whiteboard: [tracking] [Australis:P3-] → [tracking] [Australis:P-]
5 years ago
No longer blocks: australis
Whiteboard: [tracking] [Australis:P-] → [tracking]
5 years ago
Depends on: 1009021
Any updates on this? Been quite a long time since I saw some activity here and Downloads panel still looks inconsistent compared to other menu panels like Bookmarks, History etc.
We might need contributors help here, internal resources are quite limited and we are busy with higher priorities atm :/
This is sort of on my todo list, but I've got a lot of stuff to do on Servo first, and one other Firefox bug. Will take time.
Still nothing? It's been more than half of the year since u guys were talking about this issue. Downloads panel is quite front faced feature like bookmarks or history and should be unified with them. I wouldn't say a word if it would be some low level menu, but that's not the case.
I've added the design spec bug to the suggestions for the 39.1 iteration.
It is quite strange to see some deep level windows being unified (e.g. Addons unified with Options recently) while something like Downloads panel is still untouched - for such a long time. I believe that Downloads button is often placed on navigation panel or some other quite accessible place and used almost everyday - compared to Addons window, which is often used just once - to set up addons and being left untill some addon stop working because its outdated. Don't get me wrong, I like all such changes. I'm just surprised by priorities. It's something like arrow pointing from panels (Downloads, History, etc.) to its button. This arrow is touching button exactly on its border. Screenshot: http://fii.cz/maqav Arrow from app menu however overlaps the button by few pixels. Again, cosmetic bug which is being untouched by ages. Screenshot: http://fii.cz/sqcrc
(In reply to Roman Müller from comment #14) > It is quite strange to see some deep level windows being unified (e.g. > Addons unified with Options recently) while something like Downloads panel > is still untouched - for such a long time. A lot of this work has been done by volunteers. Unfortunately, this really needs a spec and we don't have one. That's bug 1009021.
Type: defect → enhancement
Summary: Downloads panel polish → Downloads panel improvements
You need to log in before you can comment on or make changes to this bug.