Unreviewed changes
1 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: site/blink/launching-features/isolated-web-apps/index.md
Insertions: 2, Deletions: 2.
@@ -70,7 +70,7 @@
* Application Developers
* Other JavaScript-based development platforms: Electron, Node.js, Deno, Bun, etc.
-Do not request a design review from the W3C TAG as the conclusion of their [design review](https://github.com/w3ctag/design-reviews/issues/842) of IWAs was that they are not the right venue for discussing IWA-specific proposals. [Mozilla](https://github.com/mozilla/standards-positions/issues/799) and [Apple](https://github.com/WebKit/standards-positions/issues/184) are similarly disinterested in IWAs or IWA-specific APIs and so there is little value in requesting standards positions for IWA-specific capabilities.
+Do not request a design review from the W3C TAG, as the conclusion of their [design review](https://github.com/w3ctag/design-reviews/issues/842) of IWAs was that they are not the right venue for discussing IWA-specific proposals. [Mozilla](https://github.com/mozilla/standards-positions/issues/799) and [Apple](https://github.com/WebKit/standards-positions/issues/184) are similarly disinterested in IWAs or IWA-specific APIs and so there is little value in requesting standards positions for IWA-specific capabilities.
The [WinterTC](https://wintertc.org/) could be a good forum for reaching out to other JavaScript-based platforms such as Node.js, Deno and Bun.
@@ -128,6 +128,6 @@
Add a section to the template explaining why this launch is IWA-specific. You can reuse the text from the explainer section written for step 1.
-IWA-specific API launches will require an additional approval from the IWA project owners. This approval process is started by sending your "Intent to Ship" email to <a href="mailto:iwa...@chromium.org">iwa...@chromium.org</a> in addition to <a href="mailto:blin...@chromium.org">blin...@chromium.org</a>. Blink API OWNERS should wait for an IWA OWNER response before reviewing the feature.
+IWA-specific API launches will require an additional approval from the IWA project owners. This approval process is started by sending your "Intent to Ship" email to <a href="mailto:iwa...@chromium.org">iwa...@chromium.org</a> in addition to <a href="mailto:blin...@chromium.org">blin...@chromium.org</a>. Blink API OWNERS will wait for an IWA OWNER response before reviewing the feature.
Documentation for the feature should be finalized by this point. Work with Developer Relations to get an article posted to [chromeos.dev](https://chromeos.dev/). This content will move to [developer.chrome.com](https://developer.chrome.com/) when IWAs are supported on more platforms and [web.dev](https://web.dev/) when IWAs are supported by multiple browsers.
```
Change information
Commit message:
Update IWA-specific API launch process
Some updates based on experience from working through a few IWA-specific
API launches and responses from the TAG and other browser vendors.
Change-Id: Ie6a2654c9288ffa3673f21589c14736506a65e5b
Files:
- M site/blink/launching-features/isolated-web-apps/index.md
Change size: S
Delta: 1 file changed, 7 insertions(+), 5 deletions(-)
Branch: refs/heads/main
Submit Requirements:
Code-Review: +1 by Jeffrey Yasskin, +1 by Mike Taylor