Topsite image only appears after clicking on a new tab
Categories
(Firefox :: Top Sites, defect)
Tracking
()
People
(Reporter: muirpablo, Unassigned, NeedInfo)
Details
(Keywords: regressionwindow-wanted)
Attachments
(2 files)
tx3.png
Tested on
Windows 10 64bit
Firefox Nightly 87.0a1 : affected
Firefox beta 86.0b9 not affected
Firefox releas 85.0.2 not affected
steps
- use the attached profile, its a profile taken from firefox nightly 85. with only 3 websites in history.
- Launch Nightly 87 with the used profile + Remotesettings OFF + Dump True
- Add a new topsite www.sony.com
- close Firefox and edit user.js to turn: Remotesettings ON
- Launch firefox
- open new tab
Expected results
sony icon should appear on step 5
actual results
there is no image on sony, only appears after clicking on a new tab.
Notes
I see the same issue of missing images with ¨manual topsite added + Historical browsed websites that appear on topsites icons but having dump off also. For example:
a. Running nightly 85 > and opening some websites, and then closing firefox.
b. Then opening Nightly 87 using the 85 profile and user.js Remotesettings false + Dump false
c. All images will load then i added a new topsite like www.sony.com
d. Then i close firefox, edit user.js and to remotesettings ON + dump false
e. When i launch firefox again the sony image is missing, + many other historical topsites visited are missing image too.
f. If i click on a new tab, all images appear.
|
||
Comment 2•3 years ago
|
||
This sounds unrelated to remote settings. Also, this might just be expected behavior. The thumbnail service fetches screenshots of sites without icons and it might take some time for them to appear. Are you sure 86 and 85 are not affected?
Hi Dão
yea i just tried again all steps with latest beta and latest release.
step#1 made used profile with browsing history with an older version of firefox, One with Release firefox-84.0.2, and another one with Beta firefox-84.0b8
Then Step#2 i used Firefox Latest beta (with the step#1 beta profile) and Latest release with (with step#1 release profile) followed the rest of steps.
On beta and release i see the image and there is no need to open a new tab to see sony.
|
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
Hi Adrian
I have been trying since last week to get a regression range using mozregression but i can´t make it work.
For example i tried to reproduce the issue in mozregression but as soon as i launch firefox from cmd having the profile modified, it launches firefox again but i don´t get a newtab page.... I see a whats new page or wellcome page in nightly.
After that if i open new tab: i see the icons appear, but opening a new tab is not good since the issue fixes itself by opening a new tab.
|
||
Comment 5•3 years ago
|
||
Unfortunately mozregression isn't helpful at all for getting a regression range here. The only way left to go at it is to manually and giving it two tries on Win10 left me with confusing results. I will have to dig a bit more into this bug.
|
|
||
Comment 6•3 years ago
|
||
I don't feel like we're getting anywhere here.
Pablo and I gave another run on 85.b4, 86.b4, 87.b9 and Nightly88, Nightly 87 and we kept getting random results with the manually added tile icons and we can't figure out or narrow down at this point what the cause is.
I think we need to narrow more towards a reduced testcase that reproduces the issue consistently and maybe hope that mozregression would also reflect the results.
Therefore, at this point its reproduction is inconsistent and we're not even sure if we're looking at a recent regression. Further more, from our tests, only the manually added tiles are affected, so from severity point of view, let's rank it s3 until we get more actionable details here. Also, removing the blocking metas since this seems to be unrelated to the switch to remote settings.
A possible candidate that might add to some of the comment 0 described behavior might be bug 1680531, but it's uncertain atm. A small regression has been logged: bug 1698099
Description
•