taskbar preview's favicon appears blank

NEW
Unassigned

Status

()

Core
Widget: Win32
29 days ago
23 days ago

People

(Reporter: ershiwo, Unassigned)

Tracking

59 Branch
x86
Windows 10
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

29 days ago
Created attachment 8945337 [details]
2018-01-25_141831.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180122192913

Steps to reproduce:

Enable "Show tab previews in the Windows taskbar" feature, and move your cursor to taskbar.


Actual results:

All favicons of multitabs appear blank, not only built-in pages.

Updated

29 days ago
Component: Untriaged → Widget: Win32
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → x86

Comment 1

27 days ago
I was able to reproduce this bug:

1) Start Firefox and open two tabs (https://www.google.com and https://www.mozilla.org for example)
2) Open about:preferences and enable the following option: "Show tab previews in the Windows taskbar"
3) Hover the mouse over the Firefox icon in the taskbar.

Expected result: The favicons are shown on the upper left corner of the tab previews.
Actual result: The default icon is displayed on the upper left corner of the previews.

The problem can be reproduced on the latest available Nightly: 20180127100319

Latest nightly WITHOUT this bug is: 20171127100433
First nightly in which this bug appeared is: 20171127220446
Status: UNCONFIRMED → NEW
Ever confirmed: true
What did you use the get that regression range? mozregression will automatically output a link that includes the changesets between those two builds which would be very helpful.
(Reporter)

Comment 3

24 days ago
(In reply to Timothy Nikkel (:tnikkel) from comment #2)
> What did you use the get that regression range? mozregression will
> automatically output a link that includes the changesets between those two
> builds which would be very helpful.

OK, I will have a try.
(Reporter)

Comment 4

24 days ago
(In reply to ershiwo from comment #3)
> (In reply to Timothy Nikkel (:tnikkel) from comment #2)
> > What did you use the get that regression range? mozregression will
> > automatically output a link that includes the changesets between those two
> > builds which would be very helpful.
> 
> OK, I will have a try.

I have run the mozregression with new profiles and got the changesets between ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2 and 16dfec69b8b0e4c70f3438db5043dcd0b7bc97f0.

The last good beta build: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2&tochange=0c5a115449a3e470307b83d92531c84c23382951
The bad beta build: https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2&tochange=16dfec69b8b0e4c70f3438db5043dcd0b7bc97f0

Any other information that I could provide? I have never use mozregression before.
(In reply to ershiwo from comment #4)
> (In reply to ershiwo from comment #3)
> > (In reply to Timothy Nikkel (:tnikkel) from comment #2)
> > > What did you use the get that regression range? mozregression will
> > > automatically output a link that includes the changesets between those two
> > > builds which would be very helpful.
> > 
> > OK, I will have a try.
> 
> I have run the mozregression with new profiles and got the changesets
> between ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2 and
> 16dfec69b8b0e4c70f3438db5043dcd0b7bc97f0.
> 
> The last good beta build:
> https://hg.mozilla.org/releases/mozilla-beta/
> pushloghtml?fromchange=ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2&tochange=0c5a
> 115449a3e470307b83d92531c84c23382951
> The bad beta build:
> https://hg.mozilla.org/releases/mozilla-beta/
> pushloghtml?fromchange=ae8dbca85bfec5b3e53e578b5c65b0effbeccdc2&tochange=16df
> ec69b8b0e4c70f3438db5043dcd0b7bc97f0
> 
> Any other information that I could provide? I have never use mozregression
> before.

Thanks for doing that!

I'm a little confused how you got a regression window on the mozilla-beta tree. Usually mozregression will work on mozilla-central (what nightly is built from). That would allow a much smaller regression window with less changes in it. I scanned the list of changes in your link and nothing stood out at me that might cause this. Is there any chance you could try again on mozilla-central?
(Reporter)

Comment 6

23 days ago
(In reply to Timothy Nikkel (:tnikkel) from comment #5)
> (In reply to ershiwo from comment #4)
> > (In reply to ershiwo from comment #3)
> > > (In reply to Timothy Nikkel (:tnikkel) from comment #2)
> 
> Thanks for doing that!
> 
> I'm a little confused how you got a regression window on the mozilla-beta
> tree. Usually mozregression will work on mozilla-central (what nightly is
> built from). That would allow a much smaller regression window with less
> changes in it. I scanned the list of changes in your link and nothing stood
> out at me that might cause this. Is there any chance you could try again on
> mozilla-central?

I have run another test on mozregression:
The last good build: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c0245a5ba4ba74b16c24771dae0e50fe22443898&tochange=e60f002f07d0d40843758d40557acfc3ac6c51f3
The first bad build: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ada1b4b1951bbe29bae0f0259c17adff1f31de7e&tochange=e60f002f07d0d40843758d40557acfc3ac6c51f3

Hopes they will help you to find where's the problem.
Thank you.
Blocks: 1420223
You need to log in before you can comment on or make changes to this bug.