Open Bug 1336858 Opened 8 years ago Updated 2 years ago

New Tab Top Sites doesn't distinguish between multiple sites on same server

Categories

(Firefox :: New Tab Page, defect, P5)

51 Branch
defect

Tracking

()

UNCONFIRMED
Tracking Status
firefox57 --- wontfix

People

(Reporter: kevin, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170125094131 Steps to reproduce: Go to two different sites at the same address that use different port numbers frequently enough to show up on Top Sites on the New Tab page. For example: http://localhost:8000 http://localhost:8080 Actual results: Only one of these will show up on New Tab. Each time you use a different one, it replaces the other. Expected results: The two different sites should have shown up separately in the list, even though they are at the same server address. Sites need to be tracked down to the port number.
Component: Untriaged → New Tab Page
This is intentional, as we dedup Top Sites across domains to avoid duplication.
I am not surprised that it's intentional. However, you are not avoiding duplication with this. I am not talking about multiple pages on the same server, I am talking about different hosts. Even if the domain name is the same, different port numbers usually mean entirely different websites. I have several cases of this and have to use an extension to get a working top sites page. Top Sites should mean Top Sites not Top Domains. Imagine if www.google.com and mail.google.com were treated as the same site. (Maybe they are.)
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.