Add Isolated Contexts spec to specs.json #1464
Conversation
|
hi @robbiemc thanks for the PR - the preferred way to add specs to browser-specs is now to use the issue template, since that allows to detect more issues; I've done so in #1466 and generated #1467 out of it - note in particular that I'm suggesting to not add (currently) the spec as a spec expected to be implemented in browsers since its deployment seems so far to be limited to ChromeOS. I've also filed WICG/isolated-web-apps#49 to help reducing the risks that the monkey patches in the spec interfere with the data extracted from the current specs. |
|
Thanks for creating the issue. Isolated Contexts are currently implemented cross-platform in chromium, and can be enabled with a flag on all desktop platforms, but are only launching on ChromeOS for the short to medium term. We plan on eventually launching to on other platforms in the future. It is intended to be a browser feature, just not enabled on all platforms for now. I'm not opposed to removing the "browser" category if that generally implies enablement cross-platform, I just want to give more context. |
Close #1466, adding the suggested spec to the list. Spec is added as a non-browser spec for now as it is ChromeOS only. That may need to be revisited later on when the spec starts being deployed to more platforms, see: #1464 (comment)
|
The spec was added to the list (will appear in browser-specs later today). The |
No description provided.