Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RealFavicon API now returns different set of favicons #2801

Closed
willgearty opened this issue Oct 24, 2024 · 0 comments · Fixed by #2804
Closed

RealFavicon API now returns different set of favicons #2801

willgearty opened this issue Oct 24, 2024 · 0 comments · Fixed by #2804

Comments

@willgearty
Copy link

willgearty commented Oct 24, 2024

It looks like the RealFavicon API has changed (probably associated with this), because it no longer returns the same set of favicons. Of the hardcoded filenames in the BS5 template, only "apple-touch-icon.png" is still returned:

<link rel="icon" type="image/png" sizes="16x16" href="{{#site}}{{root}}{{/site}}favicon-16x16.png">
<link rel="icon" type="image/png" sizes="32x32" href="{{#site}}{{root}}{{/site}}favicon-32x32.png">
<link rel="apple-touch-icon" type="image/png" sizes="180x180" href="{{#site}}{{root}}{{/site}}apple-touch-icon.png" />
<link rel="apple-touch-icon" type="image/png" sizes="120x120" href="{{#site}}{{root}}{{/site}}apple-touch-icon-120x120.png" />
<link rel="apple-touch-icon" type="image/png" sizes="76x76" href="{{#site}}{{root}}{{/site}}apple-touch-icon-76x76.png" />
<link rel="apple-touch-icon" type="image/png" sizes="60x60" href="{{#site}}{{root}}{{/site}}apple-touch-icon-60x60.png" />

This then causes the favicon to not render on some devices (e.g., Chrome/Edge on Windows). Here's the website I've recently built for my new R package as an example: https://williamgearty.com/deeptimedata. The list of favicons as built by build_favicons() can be seen here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant