Closed Bug 1112018 Opened 10 years ago Closed 5 years ago

Suggestion to make the new tab page more organized

Categories

(Firefox :: New Tab Page, defect)

35 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: johnsmith.81, Unassigned)

References

Details

(Keywords: ux-consistency, ux-minimalism)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20141211142524 Steps to reproduce: Open the new tab page. Actual results: When you frequently visit many pages within the same site, each of them will get an individual thumbnail on the new tab page, which is very messy. Expected results: The pages should be grouped by domain/subdomain, displaying only one thumbnail that points to the homepage of that site, similar to what Chrome and IE do.
Component: Untriaged → New Tab Page
Version: 34 Branch → 35 Branch
I thought the page already did this... Drew?
Flags: needinfo?(adw)
I thought so too! But looking at my own newtab page it's clearly not happening. Bug 990322 did squash URLs so that only one URL per eTLD+1 would appear, but then bug 1045760 quickly reverted that in favor of a much weaker form of squashing: http://mxr.mozilla.org/mozilla-central/source/toolkit/modules/NewTabUtils.jsm?rev=6776f88e29be#1169
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(adw)
OS: Windows 7 → All
Hardware: x86 → All
See Also: → 1045760
Can we get away with more squashing here without breaking the requirements for bug 1045760, and if so, can you outline how much, so that we can backlog and fix this? :-)
Flags: needinfo?(adw)
Flags: firefox-backlog+
Bug 1045760 seems like not a great solution to the problem described there, but I may be missing some context, and I CC'ed Ed and Dao in case they have thoughts. If the problem is only enhanced tiles, then maybe we could still squash eTLD+1's that don't map to any enhanced tile. I'll take a look.
Flags: needinfo?(adw)
Ed, what do you think of this? Go back to squashing eTLD+1's ("base domains"), but introduce link.dontSquash so the provider can say, Don't squash mah links. Note that the filter() function still adds dontSquash'ed links to the baseDomains set, so if a mozilla.org dontSquash link is ordered before a non-dontSquash mozilla.org link, then the latter won't appear. Not sure whether that's good or not. If you think this is fine, then maybe extractSite should be moved to DirectoryLinksProvider.jsm?
Attachment #8546839 - Flags: feedback?(edilee)
There were various complaints about having subdomains squashed into a single tile like bug 1045760 comment 5. E.g., bugzilla, mdn, www, amo, air, etc. all squashed into whichever mozilla.org link was highest. To be clear, the current functionality shows one tile per subdomain squashing multiple links with different paths to the higher ranked link. That seems to match up with comment 0's expected "The pages should be grouped by domain/subdomain"
Hmm, I think I jumped to conclusions from comment 0. John, are you asking for www.mozilla.org/foo and www.mozilla.org/bar to be squashed into the same tile, or are you asking for foo.mozilla.org and bar.mozilla.org to be squashed into the same tile? As Ed says, the former should be happening now but not the latter, by design.
Flags: needinfo?(johnsmith.81)
Attachment #8546839 - Flags: feedback?(edilee)
Flags: needinfo?(johnsmith.81)

Hello!

This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.

Please help us triage by reopening if this issue still persists and should be addressed.

Thanks!

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: