Bug 1984236 Comment 3 Edit History

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

Also quite notable here...

(In reply to Daniel Holbert [:dholbert] from comment #1)
> 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.

So: if I go to docs.new (just going there directly for simplicity, since that's more consistent in Firefox & Chrome), and I tap through the in-content "USE THE APP" button and click through the launch-external-app prompt (you might have to force-quit Firefox in order to get the prompt to appear, per bug 1847273), then Google Docs opens with just a prompt that says:
```
Oops
Document lookup failed. It is possible the document was deleted
[OK]
```

This is true regardless of whether I'm using Firefox or Chrome.  So: docs.new isn't really usable at all regardless of which browser you're using (which is unfortunate because it's where docs.google.com shuttles Firefox users if they decline its initial "launch external app" prompt).
Also quite notable here...

(In reply to Daniel Holbert [:dholbert] from comment #1)
> 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.

Let's say on the other hand you *do* want to launch the app -- if you go to docs.new (let's say you type that URL into your URL bar, for simplicity, since that's more consistent in Firefox & Chrome), and you end up looking at a blank google-doc with an edit icon, and you tap the edit icon and tap through the in-content "USE THE APP" button, and click through the launch-external-app prompt (you might have to force-quit Firefox at this point in order to get the prompt to appear, if you've previously declined a prompt, per bug 1847273): then the Google Docs app opens with just a prompt that says:
```
Oops
Document lookup failed. It is possible the document was deleted
[OK]
```

This is true **regardless of whether I visited docs.new in Firefox or Chrome**.  So: docs.new isn't really usable at all regardless of which browser you're using (which is unfortunate because it's where docs.google.com shuttles Firefox users if they decline its initial "launch external app" prompt).
Also quite notable here...

(In reply to Daniel Holbert [:dholbert] from comment #1)
> 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.

Let's say on the other hand you *do* want to launch the app -- if you go to docs.new (let's say you type that URL into your URL bar, for simplicity, since that's more consistent in Firefox & Chrome), and you end up looking at a blank google-doc with an edit icon, and you tap the edit icon and tap through the in-content "USE THE APP" button, and click through the launch-external-app prompt (you might have to force-quit Firefox at this point in order to get the prompt to appear, if you've previously declined a prompt, per bug 1847273): then the Google Docs app opens with just a prompt that says:
```
Oops
Document lookup failed. It is possible the document was deleted
[OK]
```

This is true **regardless of whether I visited docs.new in Firefox or Chrome**.  So: the docs.new website isn't really usable at all (can't edit in the webapp, can't usefully spawn external app) regardless of which browser you're using (which is unfortunate because it's where docs.google.com shuttles Firefox users if they decline its initial "launch external app" prompt).
Also quite notable here...

(In reply to Daniel Holbert [:dholbert] from comment #1)
> 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.

Let's say on the other hand you *do* want to launch the app -- if you go to docs.new (let's say you type that URL into your URL bar, for simplicity, since that's more consistent in Firefox & Chrome), and you end up looking at a blank google-doc with an edit icon, and you tap the edit icon and tap through the in-content "USE THE APP" button, and click through the launch-external-app prompt (you might have to force-quit Firefox at this point in order to get the prompt to appear, if you've previously declined a prompt, per bug 1847273): then the Google Docs app opens with just a prompt that says:
```
Oops
Document lookup failed. It is possible the document was deleted
[OK]
```

This is true **regardless of whether I visited docs.new in Firefox or Chrome**.  So: the docs.new website isn't really usable at all (can't edit in the webapp, can't usefully spawn external app) regardless of which browser you're using.  (Though this is still particularly unfortunate for us for us because docs.new happens to be where docs.google.com shuttles Firefox users if they decline its initial "launch external app" prompt as described in comment 1.)
Also quite notable here...

(In reply to Daniel Holbert [:dholbert] from comment #1)
> 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.

Let's say on the other hand you *do* want to launch the app -- if you go to docs.new (let's say you type that URL into your URL bar, for simplicity, since that's more consistent in Firefox & Chrome), and you end up looking at a blank google-doc with an edit icon, and you tap the edit icon and tap through the in-content "USE THE APP" button, and click through the launch-external-app prompt (you might have to force-quit Firefox at this point in order to get the prompt to appear, if you've previously declined a prompt, per bug 1847273): then the Google Docs app opens with just a prompt that says:
```
Oops
Document lookup failed. It is possible the document was deleted
[OK]
```

This is true **regardless of whether I visited docs.new in Firefox or Chrome**.  So: the docs.new website isn't really usable at all (can't edit in the webapp, can't usefully spawn external app) regardless of which browser you're using.  (Though this is still particularly unfortunate for us for us because docs.new happens to be where docs.google.com ultimately shuttles Firefox users if they decline its initial "launch external app" prompt as described in comment 1.)

Back to Bug 1984236 Comment 3