Re: [w3c/manifest] Clarify rule of navigating away from the navigation scope (#646)

I've updated Killer Marmot (our testing PWA) to prove why this needs to change. (Note: This change is *not* being made for compat with any particular implementation, though it happens to align to recent versions of Chrome on Android. It's because the currently specced behaviour breaks expectations of existing sites.)

Test site: https://killer-marmot.appspot.com/web/

Steps to test:
1. Install this app and open it in a window.
2. Click "Post!" under "POST-and-redirect".
3. Should navigate to https://redirectonpost.appspot.com/, showing a white page with a countdown for 3 seconds.
4. Should navigate back to Killer Marmot, which should read "I see you're back!"

Under the current spec text, step 3 *must* take place in a different browsing context (either in a separate window as we do on Chrome OS, or over the top of the app window, as Firefox for Android does and Chrome for Android used to do.) Step 4 *must* therefore take place in that secondary browsing context, or some complex non-standard machinery catches the redirect back and moves back into the original app context.

Under the proposed spec text, step 3 *must* take place within the original app context (but we highly recommend showing "redirectonpost.appspot.com" to highlight the off-scope origin). Step 4 should therefore naturally also take place within the original app context, with no origin display because you're back inside the app scope.

-- 
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/issues/646#issuecomment-402946834