737358 - [New Tab Page] don't display redirect sources

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, defect)

Description

[Kadir Topal [:atopal]]

The new tab page page feature is great, but it displays redirects next to the actual page, so spiegel.de is next to www.spiegel.de. There are two issues with this:

1. spiegel.de is displayed as a blank page, which makes sense, since it always only redirects to www.spiegel.de

2. Having the urls next to each other provides no benefit whatsoever and takes away the space that could be used by other pages. From my top 9 pages, 3 are blank redirects.

It can be tricky to figure out which one to display, the plain one or the one with www. I have daringfireball.net in my top list, but that redirects from wwww.daringfireball.net to firefball.net. So, I guess my suggestion is, see if any of the two destinations is a blank page, only display the real one. If both of them have real content, display both.

Comment 1

[Tim Taubert [:ttaubert] (inactive)]

(In reply to Kadir Topal [:atopal] from comment #0)
> 1. spiegel.de is displayed as a blank page, which makes sense, since it
> always only redirects to www.spiegel.de

That's bug 705911.

> 2. Having the urls next to each other provides no benefit whatsoever and
> takes away the space that could be used by other pages. From my top 9 pages,
> 3 are blank redirects.

Indeed.

So I suppose you're using Firefox Sync? The new tab page is supposed to only display redirect targets *but* that information gets lost when these hits are synced from another device. So they're not counted as redirect sources but normal hits which then lets those appear on the new tab page. That should be bug 559175 which seems far from being fixed :/

Comment 2

[Kadir Topal [:atopal]]

Just for clarification: Yes, I am a sync user.

Comment 6

[Matthew N. [:MattN]]

Mass-move to Firefox::New Tab Page.

Filter on new-tab-page-component.

Comment 9

[Jessilyn Davis]

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!