- From: Daniel Murphy <notifications@github.com>
- Date: Thu, 29 Oct 2020 11:59:10 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 29 October 2020 18:59:23 UTC
@dmurph commented on this pull request. > @@ -1044,6 +1110,7 @@ <h2> DOMString iarc_rating_id; USVString start_url; DisplayModeType display = "browser"; + sequence<DisplayModeType> display_override; Based on internal implementation experience, it will be much easier to present this as the other option, where the algorithm fails for any 'new' display mode in `display`. What do you think about that? I made a note under the algorithm: ``` In the future, new values added to {{DisplayModeType}} will not be added to the fallback chain, and the algorithm should treat the a {{WebAppManifest/display}} field set to a new value as {{browser}}. ``` And a note in DisplayModeType: -- 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#discussion_r514496062
Received on Thursday, 29 October 2020 18:59:23 UTC