1485938 - Top Search Site should not add promoted tiles.

Status: RESOLVED WONTFIX

(Firefox :: New Tab Page, enhancement)

Description

[Nicolas B. Pierron [:nbp]]

From tl;dr emails: "__if__ users have Google or Amazon as a Top Site".

I never visit google search nor amazon website and as such I do not expect them to be in my top websites. However, now they appears as the *promoted tiles* for doing searches. (Firefox nightly)

 - I stopped using google because I tried bing for testing, and everytime I go back to google they offer me their flat design UI which is too awful to be useful.
 - I only use amazon under private browsing because they are incapable of respecting Do-Not-Track.

So having both of these tiles appearing really fills like promoted tiles and I wish the __if__ of tl;dr email were to be respected.

However, I would really appreciate search shortcuts feature for all websites which have a search box and which are already part of my top sites, such as: 
  gmail, phonebook, github, mana, google groups, bugzilla, twitter, crates.io and searchfox.

Comment 1

[Nicolas B. Pierron [:nbp]]

I will note that my profile is not new, at least 6 months old, and connected to an older Firefox Account.
So maybe there is a bug related to adding @Google and @Amazon to new profiles, which also affected my current profile.

Comment 2

[Maria Popova]

Thanks for the feedback!

We'll be running an experiment with the new feature and gathering results (incl. sentiment analysis) prior to launching globally.

We do allow users to remove these new Top Sites and provide a choice of other supported search engines from the section ("Add Search Engine" has a list of the 7 most popular ones.

Comment 3

[Nicolas B. Pierron [:nbp]]

Why is it marked as Won't Fix?

I noticed this issue in 2 different old Nightly profiles so far. Which does not match any of the document or bug related to this feature claimed to be doing, as far as I know, which to me qualify as a valid bug.

So, I do not understand why this bug is being marked as "won't fix" if this is not the intended behaviour.

Comment 4

[Nicolas B. Pierron [:nbp]]

(In reply to Nicolas B. Pierron [:nbp] from comment #3)
> Why is it marked as Won't Fix?

Someone just gave me a pointer to Bug 1480509 comment 4, which explains why this was made this way and not as it was originally documented.