Closed MerlinLaffitte closed 4 years ago
j'en avais parlé sur WA, given it is a warning I would ignore, unless you want to maintain 1 manifest per browser and have a specific build for each
Ok do we know how Chrome takes into account warnings in the code for the SEO?
No idea, but I'd say to ignore it for the moment. If we lose some ranks we'll decide what to do.
What
How
Possible solution could be two different manifests triggered by
npm run build-prod-ff
andnpm run build prod-chrome
or do we need to use these elements at all for FF?