RESOLVED INVALID 246327
Icon on start page "favorites" and "reading list" only works with real certificates
https://bugs.webkit.org/show_bug.cgi?id=246327
Summary Icon on start page "favorites" and "reading list" only works with real certif...
fredrik kortetjärvi
Reported 2022-10-11 02:44:46 PDT
Created attachment 462922 [details] Screenshot showing the working and not working icons on the start page This is only tested on macOS 12.6 with safari 16.0. When using self signed certificate it does not show the icons in the start page on either "favorites" or "reading list". We trusted our own certificate like this: Download the certificate to the mac and open the KeyChain and trusted the certificate added it in "system" chain and then trusted all. Then the favicons in the tabs and bookmarks in the booksmarks menu worked fine, and the site have padlock when on it and safari say it self it trusted. Everything else from "favorites" and "reading list" icons works fine what we could tell. Safari doesn't complain at all about this self signed certificate at this point. To identify this we set up a site with LetsEncrypt certificate and then "favorites" and "reading list" icons start working. Why does the "favourites" and "reading list" icons work differently here w.r.t the certificate?
Attachments
Screenshot showing the working and not working icons on the start page (210.63 KB, image/png)
2022-10-11 02:44 PDT, fredrik kortetjärvi
no flags
this is the favicon we used (346.16 KB, image/x-icon)
2022-10-11 02:47 PDT, fredrik kortetjärvi
no flags
fredrik kortetjärvi
Comment 1 2022-10-11 02:47:03 PDT
Created attachment 462923 [details] this is the favicon we used added like this in html code <link rel="icon" type="image/x-icon" href="app/images/icons/icon.ico">
Alexey Proskuryakov
Comment 2 2022-10-12 11:23:30 PDT
Thank you for the report! Favorites and Reading list are Safari features, not WebKit ones. Could you please report this to Apple via https://feedbackassistant.apple.com ?
linma
Comment 3 2022-11-28 07:46:33 PST
Note You need to log in before you can comment on or make changes to this bug.