Re: [w3c/manifest] Feature request: "isolate web app" hint (Issue #1109)

I thought about that (the "list of strings" advice coming from our previous problem with extending `display` and having to add a new `display-override` member to allow sites to fall back to an existing one). I don't think it's necessary in this case - we aren't creating a potentially-ever-growing list of options, just a boolean (possibly with a tri-value "yes", "no", "unspecified default").

If we decide to not include "no-isolate" but keep it as an option for the future, we don't need a fallback chain, because "no-isolate" will implicitly fall back to the default, which is to not isolate, except for Policy 2 which doesn't give the site a choice.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1109#issuecomment-1899449956
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1109/1899449956@github.com>