Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Wrong best practices warning about manifest short_name when testing non-pwa websites
See original GitHub issueI am checking ordinary static websites, NOT progressive web apps (not pwa), the Progressive Web App is NOT selected when I start the audit, but when the audit finishes I still get:
Manifest’s
short_namewill be truncated when displayed on homescreen
under the Best Practices. It does not matter whether I select desktop or mobile device; I still get this wrong warning. The warning does not make any sense to me: There is not any short_name since there is not any web app manifest, so the short_name cannot possible be truncated because there is not any.
In my opinion, the only case when this message could make sense is when I audit Progressive Web Apps.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Good news, this was fixed in #4860, which shipped with Lighthouse 3.0 😃 If you’re running Lighthouse in DevTools, you shouldn’t see this happen in current stable Chrome (m69).
@brendankenny Awesome, thank you!