(In reply to eight04 from comment #0) > It seems that Firefox started using apple-touch-icon for bookmark icons. It always did, though the bug you linked to should have done exactly the opposite. Looking at the database the rich flag is correctly set, it's likely we inadvertently inverted the condition. This is luckily non destructive, a week after we land a fix favicons should go back to normality. Yazan, could you please check this?
Bug 1917470 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to eight04 from comment #0) > It seems that Firefox started using apple-touch-icon for bookmark icons. It always did, though the bug you linked to should have done exactly the opposite (prioritize non rich icons). Looking at the database the rich flag is correctly set, it's likely we inadvertently inverted the condition. This is luckily non destructive, a week after we land a fix favicons should go back to normality. Yazan, could you please check this?
(In reply to eight04 from comment #0) > It seems that Firefox started using apple-touch-icon for bookmark icons. It always did, though the bug you linked to should have done exactly the opposite (prioritize non rich icons). Looking at the database the rich flag is correctly set, it's likely we inadvertently inverted the condition. This is luckily non destructive, a fix should be immediately effective. Yazan, could you please check this?