Closed
Bug 1213140
(top-sites)
Opened 9 years ago
Closed 3 years ago
[meta] Improve quality of Top Sites panel grid
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: antlam, Unassigned)
References
Details
(Keywords: meta)
Filing to keep track of some polish we're looking at for the Top Sites panel specifically.
Comment 1•9 years ago
|
||
(In reply to Anthony Lam (:antlam) from comment #0) > Filing to keep track of some polish we're looking at for the Top Sites panel > specifically. I would rather have a smaller meta bug whose scope is "make top sites more useful", and this can include things like grouping by domain. While updating the UI is important, I think updating the order of the sites to be more useful would have more impact on users, so I wouldn't want to block shipping that.
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to :Margaret Leibovic from comment #1) > I would rather have a smaller meta bug whose scope is "make top sites more > useful", and this can include things like grouping by domain. > > While updating the UI is important, I think updating the order of the sites > to be more useful would have more impact on users, so I wouldn't want to > block shipping that. I'm OK with either. Feel free to create another [meta] for the backend/ ordering work if you'd like. :) I will probably need this to track the different aspects of visual clean up we want to do. But, I _do_ think it's valuable for users to see an immediate change as well as feel/notice improved usefulness overtime. Especially, considering the high visibility of this Top Sites panel on First Run. I'd like to see if we can improve that UX.
Updated•8 years ago
|
Summary: [meta] Update Top Sites panel → [meta] Improve quality of Top Sites panel grid
Comment 3•8 years ago
|
||
I think we should prioritize some of the smaller pieces of work here. There are bigger things that can make this better (e.g. distinguish local/remote visits), but there is also work we can do to chip away at this overall crummy experience.
Flags: needinfo?(bbermes)
Comment 4•8 years ago
|
||
Margaret, do you have any specific sub-bugs in mind or just for us to go through it in our next meeting and break it down and prioritize? I'm sure I can find some of my favourites to work on first. I wouldn't mind checking some reviews or SUMO articles to see what people like/don't like.
Flags: needinfo?(bbermes) → needinfo?(margaret.leibovic)
Comment 5•8 years ago
|
||
(In reply to Barbara Bermes [:barbara] from comment #4) > Margaret, do you have any specific sub-bugs in mind or just for us to go > through it in our next meeting and break it down and prioritize? I think we should implement the 3-column top sites grid and move away from using thumbnails. We have lots of quality issues associated with our thumbnails (or the lack thereof appearing), so it would be nice to be able to drop that support. Along with switching to using favicons, we should invest in making sure we're getting high quality favicons, and apply nicer looking treatments when we don't have a favicon. Separate from these visual changes, we should also make the set of sites that appears here more useful. Grisha is already working on eliminating desktop sites (bug 1046709), but we could also do thinks like avoid duplicate sites (bug 1254660) and grouping sites by domain (bug 1237038).
Flags: needinfo?(margaret.leibovic)
Comment 6•8 years ago
|
||
I'm trying to make sense of all our home panels bugs and their dependencies... Sebastian, can you help me clean up the dependency tree here? I think some of these can probably be closed as we transition to the new 3-column top sites design. This current bug tree also encompasses some of the work Grisha is doing to make the our top sites query smarter, I think that could be split off into its own little project.
No longer blocks: home-panels
Flags: needinfo?(s.kaspari)
Updated•8 years ago
|
Flags: needinfo?(s.kaspari)
Reporter | ||
Updated•8 years ago
|
Alias: top-sites
Comment 7•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•