- From: Tiger Oakes <notifications@github.com>
- Date: Thu, 29 Oct 2020 22:59:50 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 30 October 2020 06:00:03 UTC
I'm OK with not allowing new values in `display`. The resolution from TPAC was that implementors would allow `display` to be omitted if `display_override` is present, allowing it to work like a display v2. I'm concerned about how to teach this to a new dev who isn't concerned about the backwards compat, and requiring two separate display fields makes it more confusing. -- 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/pull/932#issuecomment-719237911
Received on Friday, 30 October 2020 06:00:03 UTC