Bug 1984236 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

FWIW I'm seeing a similar experience in Chrome as in Firefox, except that the choice to launch the app at one of the steps isn't optional there, which happens to smooth over some rough edges in the gooogle workspace web of sites.

Specifically:
1. docs.google.com redirects to https://workspace.google.com/products/docs/ (in both Chrome and Firefox)
2. That page has a sign in button, which is really just a link to https://docs.new/
3. when I tap that link, Chrome launches the docs app, while Firefox *invites* me to launch the docs app. If I decline the launch in Firefox, I end up just looking at the actual web version of https://docs.new/ which makes sense
4. (In Chrome, if I directly load docs.new, I get the same experience as in Firefox from here on out)
5.  docs.new redirects to a blank doc with a edit button. The edit button doesn't directly work in Firefox or Chrome - it spawns an in-content invitation to launch the external app, but you can't edit if you don't want to launch the app.
6. There's a back button which points to a drive.google.com url, which invites me to launch that app (or auto launches in Chrome). If I decline the launch in Firefox, I end up at the web version of Google Drive, which makes sense.
FWIW I'm seeing a similar experience in Chrome as in Firefox, except that the choice to launch the app at one of the steps isn't optional there, which happens to smooth over some rough edges in the gooogle workspace web of sites.

Specifically:
1. docs.google.com redirects to https://workspace.google.com/products/docs/ (in both Chrome and Firefox)
2. That page has a sign in button, which is really just a link to https://docs.new/
3. when I tap that link, Chrome launches the docs app, while Firefox *invites* me to launch the docs app. If I decline the launch in Firefox, I end up just looking at the actual web version of https://docs.new/ which makes sense
4. (In Chrome, if I directly load docs.new, I get the same experience as in Firefox from here on out, minus the 302 redirect)
5.  docs.new shows "302 moved" with a link, which ultimately (sometimes requiring multiple taps) redirects to a blank doc with a edit button. The edit button doesn't directly work in Firefox or Chrome - it spawns an in-content invitation to launch the external app, but you can't edit if you don't want to launch the app.
6. There's a back button which points to a drive.google.com url, which invites me to launch that app (or auto launches in Chrome). If I decline the launch in Firefox, I end up at the web version of Google Drive, which makes sense.
FWIW I'm seeing a similar experience in Chrome as in Firefox, except that the choice to launch the app at one of the steps isn't optional there, which happens to smooth over some rough edges in the gooogle workspace web of sites.

Specifically:
1. docs.google.com redirects to https://workspace.google.com/products/docs/ (in both Chrome and Firefox)
2. That page has a sign in button, which is really just a link to https://docs.new/
3. when I tap that link, Chrome launches the docs app, while Firefox *invites* me to launch the docs app. If I decline the launch in Firefox, I end up just looking at the actual web version of https://docs.new/ which makes sense (though its sometimes a redirect, see below)
4. (In Chrome, if I directly load docs.new, I get the same experience as in Firefox from here on out, minus the 302 redirect)
5.  docs.new shows "302 moved" with a link, which ultimately (sometimes requiring multiple taps) redirects to a blank doc with a edit button. The edit button doesn't directly work in Firefox or Chrome - it spawns an in-content invitation to launch the external app, but you can't edit if you don't want to launch the app.
6. There's a back button which points to a drive.google.com url, which invites me to launch that app (or auto launches in Chrome). If I decline the launch in Firefox, I end up at the web version of Google Drive, which makes sense.

Back to Bug 1984236 Comment 1