Bugzilla

It looks like this is a page that continuously replaces the favicon for digital art purposes. It's an edge case, but it works in other browsers.
It's imo less problematic then the original bug, as it's more confusing and dangerous to get the wrong favicon than a flickering one.

The only workaround I could think about so far, is adding a "purpose" argument to setIcon to distinguish a page load from a page icon replacement, maybe reusing again beforePageShow from FaviconLoader. Anything after pageshow would not clear the attribute and thus not flicker.
Otherwise we should undo Bug 1845035 and rather modify the image loading procedure to clear the image if the new one is unreadable, but I suspect that may affect the Web as it's loading the "image" attribute.

It looks like this is a page that continuously replaces the favicon for digital art purposes. It's an edge case, but it works in other browsers.
It's imo less problematic than the original bug, as it's more confusing and dangerous to get the wrong favicon than a flickering one.

The only workaround I could think about so far, is adding a "purpose" argument to setIcon to distinguish a page load from a page icon replacement, maybe reusing again beforePageShow from FaviconLoader. Anything after pageshow would not clear the attribute and thus not flicker.
Otherwise we should undo Bug 1845035 and rather modify the image loading procedure to clear the image if the new one is unreadable, but I suspect that may affect the Web as it's loading the "image" attribute.

It looks like this is a page that continuously replaces the favicon for digital art purposes. It's an edge case, but it works in other browsers.
It's imo less problematic than the original bug, as it's more confusing and dangerous to get the wrong favicon than a flickering one.

The only workaround I could think about so far, is adding a "purpose" argument to setIcon to distinguish a page load from a page icon replacement, maybe reusing again beforePageShow from FaviconLoader. Anything after pageshow would not clear the attribute and thus not flicker. It should be as easy as letting .beforePageShow pass-through.
Otherwise we should undo Bug 1845035 and rather modify the image loading procedure to clear the image if the new one is unreadable, but I suspect that may affect the Web as it's loading the "image" attribute.