- From: Dominick Ng <notifications@github.com>
- Date: Sun, 05 Apr 2020 19:52:41 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 April 2020 02:52:54 UTC
Having discussed with @mgiuca, we are quite unlikely to add this check in Chromium. 1. If we enforce a MIME type, we can't see what the benefits are for imposing more pain on developers, or potentially putting them in a situation they can't easily fix if they don't have control over the served MIME type. 2. If we just add a warning, what is the path to removing that warning? Again, if developers can't easily fix the situation, we won't ever be able to move to enforcement, and we've just added noise. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/821#issuecomment-609539499
Received on Monday, 6 April 2020 02:52:54 UTC