manifest file extension should be webmanifest not json

[gemal]

I believe the correct extension for the manifest file is webmanifest and not json

https://developer.mozilla.org/en-US/docs/Web/Manifest

[MMB1983]

Hi,
This is very confusing as different sources give different info:
https://developers.google.com/web/fundamentals/web-app-manifest/
https://www.w3.org/TR/appmanifest/
https://developer.chrome.com/multidevice/android/installtohomescreen

I haven't checked .webmanifest type but .json type work on android just fine :-)

[alrra]

This is very confusing as different sources give different info:

I haven't checked .webmanifest type but .json type work on android just fine :-)

@mastakilla1983: @gemal Most probably opened this issue because of the sonarwhal project, that recommends the .webmanifest file extension, and the reasoning behind it is:

While the .webmanifest file extension is not enforced by the specification, nor is it required by browsers, using it makes it:

• easier to set custom server configurations for the web app manifest file
• possible to benefit from existing configurations

(from: https://sonarwhal.com/docs/user-guide/rules/rule-manifest-file-extension/#why-is-this-important)

[phbernard]

I get the point, thank you for reporting.

@alrra You seem to be involved in this question. Quick question for you: as most web servers are not configured for the .webmanifest extension, they don't send this file with the proper Content-Type. Do we know how browsers that support the manifest (eg. Chrome) react to this situation? While I value standards and best practices, I want to make sure this change won't generate regressions.

[phbernard]

Successfully tested against Windows Chrome and Android Chrome.

Deployed a minute ago.

[alrra]

@phbernard Sorry for the delayed answer.

as most web servers are not configured for the .webmanifest extension, they don't send this file with the proper Content-Type. Do we know how browsers that support the manifest (eg. Chrome) react to this situation?

Browsers (e.g.: Chrome, Samsung Internet) that have support for the web app manifest file don't actually care about what media type the file is served with, they just download it and parse it as JSON.

Deployed a minute ago.

👍

[phbernard]

@alrra That's what I observed with Chrome. Thanks for the confirmation!

[shoulders]

The post OneSignal/OneSignal-Website-SDK#332 has some useful information on this subject.

For easier content searching: site.manifest manifest.json