You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems the favicon of a domain is given precedence over a possible <icon> element in an Atom feed.
This breaks feed generator websites that allow users to create custom feeds with custom icons, since every user feed gets the same favicon instead of their custom icon.
The problem with icons specified in feeds is that they are often not square — and favicons are (pretty much always) square. The app really wants square icons!
(We will of course look into this in the future. There are things we can do. The above is just to explain why we went with favicons over icons specified in feeds in the first place.)
Problem
It seems the favicon of a domain is given precedence over a possible
<icon>
element in an Atom feed.This breaks feed generator websites that allow users to create custom feeds with custom icons, since every user feed gets the same favicon instead of their custom icon.
For example, a kill-the-newsletter feed.
I didn't test it with other feed types like RSS or JSON.
Steps To Reproduce
Add feed
https://kill-the-newsletter.com/feeds/iu8547vjdyb06za1lb1u.xml
to NetNewsWire.The feed's XML
Expected Result
The feed icon is the URL in the
<icon>
element.Actual Result
The feed icon is the
/favicon.ico
.The text was updated successfully, but these errors were encountered: