Safari 15.4 supports manifest-declared PWA icons: "Does not provide a valid apple-touch-icon" warning is now redundant!
See original GitHub issueSafari 15.4 (released March 14) added support for declaring icons in a web app manifest file. Lighthouse’s “Does not provide a valid apple-touch-icon” warning when auditing a PWA is now redundant and should be removed, as it is not necessary anymore for web developers to specify a <link rel="apple-touch-icon" />
.
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
Does not provide a valid apple-touch-icon - Chrome Developers
When iOS Safari users add Progressive Web Apps (PWAs) to their home screens, the icon that appears is called the Apple touch icon....
Read more >apple-touch-icon not showing | Apple Developer Forums
Is this a bug in Safari? Anybody an idea how to place the apple-touch-icon on the home screens of our customers without importing...
Read more >Add an Apple touch icon to your Progressive Web App
This codelab shows you how to add an Apple touch icon to a PWA. It assumes that you have access to an iOS...
Read more >PWA icons are not used in iOS 11.3 - Stack Overflow
Declaring icons in a web app manifest file is now supported. However purpose value should contain any (e.g. "any maskable" ) or omitted ......
Read more >"icon" | Can I use... Support tables for HTML5, CSS3, etc
"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The team will be deleting the audit in v10, as per discussion in issue 11458. It was already problematic as it ignored the icon’s presence in the site root.
dupe #11458