Running new profile with services.settings.load_dump false produce different results that running it with services.settings.load_dump true. This has been noted to happen only when there's a search shortcut involved in the default topsites (amazon).
Since production environment has the dump true on default, this report might end to be a low severity/priority, however the concern would be that this behavior suggests that it might be a different code-path that is triggered when data is taken from dump vs when it's updated from RS pipeline. This might have possible unwanted behaviours when updating from RS directly.
- Download Firefox en-US
- Create two profiles and do not initialize them.
- In 1st profile folder place an user.js that has: user_pref("services.settings.load_dump", false);
- Second profile has services.settings.load_dump to true, so no user.js is needed.
- Start Firefox with both profiles and compare the results.
The topsites order for dump-false profile is:
1)Youtube , 2)Amazon.com(shortcut), 3)Facebook, 4)Reddit, 5)wikipedia, 6)Twitter
The topsites order for dump-true profile is:
1)Amazon.com(shortcut), 2)Youtube, 3)Facebook, 4)Reddit, 5)wikipedia, 6)Twitter
Dump true or false should make no difference in the topsites order.
- Interesting enough, for the dump false, when you change the default search engine from google to something else (let's say bing), the @google search shortcut would be inserted in the topsites, but this will also cause the topsites to get arraged correctly:
1)Amazon.com(shortcut), 2)google(shortcut), 3)Youtube, 4)Facebook, 5)Reddit, 6)wikipedia, 7)Twitter