Steps: 1. Go to testmanifest.com 2. Install a web app that calls out support for locales, but fails to call out support for default locale Expected: Installation should fail in the core dom api saying the manifest is invalid. Actual: Installation ends up being successful. Example: { "name":"Test App ({subdomain})", "description":"This app has been automatically generated by testmanifest.com", "version":"1.0", "icons":{ "16":"http://testmanifest.com/icon-16.png", "48":"http://testmanifest.com/icon-48.png", "128":"http://testmanifest.com/icon-128.png" }, "installs_allowed_from":[ "*" ], "developer":{ "name":"Gregory Koberger", "url":"http://gkoberger.net" }, "locales":{ "es": { "name": "Override name", "developer": { "name": "Override dev name", "url": "Override url" } } } }

Fabrice said that if there's no default locale we just pick the locale selected on the device. With that workaround and the fact that we're reviewing apps that go through the marketplace, let's not block on this.

(In reply to Andrew Overholt [:overholt] from comment #1) > Fabrice said that if there's no default locale we just pick the locale > selected on the device. With that workaround and the fact that we're > reviewing apps that go through the marketplace, let's not block on this. That assumption can no longer be made. Vivo is on the radar now. So we can't assume app review process can protect this anymore.

Let's update the docs since current behavior seems quite reasonable.

(In reply to Jonas Sicking (:sicking) from comment #3) > Let's update the docs since current behavior seems quite reasonable. Fine by me. Let's close this as invalid, but I'll put dev-doc-needed to update the spec.