bclexa@ -- Thanks for reporting this issue along with the screencast. Could you please share the sample file to reproduce the issue. That would help us in further triaging the issue.

Thanks in advance!

The initially attached artwork-bug.7z has the "site" directory inside. Serve it using any http server (for example https://www.npmjs.com/package/http-server).

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

When trying to reproduce this, I can see that the red icon shows for a split second but then switches to the green one. Reason is likely because Chrome doesn't have the icon ready and fetches it. Because we want to have something to show, we will use the website icon while the media session one is being fetched.

Do you confirm this?

By the way, thanks a lot for the great test page. I've hosted it here so it's easier to test: http://mounirlamouri.github.io/sandbox/bugs/797494.html 

mlamouri, on my device (Pixel) when I follow steps captured in the screencast the red icon persists.

It's a bit flaky ineed. Better reproduced if you manage to hit play while the page loading progress bar is still visible. Could it be that the artwork is not loaded when there are other active fetches?

Thank you for providing more feedback. Adding requester "mlamouri@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I checked network activity via chrome://inspect/#devices
In the negative case, there are no requests for artwork. 
Screenshots attached.

Deleted: ok.png 134 KB

	ok.png 134 KB View Download

Deleted: fail.png 124 KB

	fail.png 124 KB View Download

Thanks for the report! :)

I confirm the issue. What probably happens is that one helper (MediaSessionTabHelper or MediaImageManager) believes that the image or metadata have not change and therefore does not attempt any update but the data is no longer available. This theory seems to be confirmed by the fact that closing the tab and opening a new one to the same page fixes the glitch.

Also moving to P3 given the tiny breakage and the tiny window in which it can occur.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot