Re: [w3c/manifest] Adding field `display_override` to the manifest (#932)

> 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 think that wouldn't be good for compat until _all_ browsers are implementing `display_override` (which is why we designed it as an override, not as a v2). Otherwise, a developer tests against, say, Chrome, uses `display_override` without considering browsers that aren't implementing it, and it doesn't behave properly on those other browsers. I think we should make it mandatory now, and we can address it again in a year or so, removing the need to have a `display` which would be backwards-compatible.

This isn't getting a lot of attention, and I'd like to set a deadline to land it in the Manifest spec. If not, I think we should move this into a WICG repo so that we can point to it without having to refer to this PR. @NotWoods are you planning to implement this in Gecko? If so, I think we can take that as a sign of multi-vendor interest, and land this as-is.

If we only have Chromium on board, then we should move it into WICG.

Should we set a deadline of EOD Friday November 20, to get approvals on this PR?

-- 
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-726476002