New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 768733 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature

Blocking:
issue 740783



Sign in to add a comment

desktop-pwas: Should submitting a form using GET open the app?

Project Member Reported by ortuno@chromium.org, Sep 26 2017

Issue description

From [1]:

ortuno: When I click on a submit button I expect the website to replace the form with a success message. I think opening the app in this case would break that expectation. Imagine submitting the form and then a new window opens with a success message, but the form is still there in the other tab.

mgiuca:
Yeah that would suck.

I think eventually it would be good to redirect all cross-site navigations into the app (so if you submit a form from Site A to Site B then it opens in the app, but if you submit a form on Site B to Site B then it stays). But this is fine now.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/661998/7/chrome/browser/extensions/bookmark_app_url_redirector_browsertest.cc


 

Comment 1 by ortuno@chromium.org, Sep 26 2017

I'm uncertain that would be the expected behavior even for cross-site navigations. Users would still be left with a filled form on Site A.

Comment 2 by mgiuca@chromium.org, Sep 26 2017

That's true. I'm happy to leave it.

Note: this sort of interaction happens in places other than forms (sites leaving themselves in bad states, expecting to be navigated away from). For example, in the Google Docs menu screen (open in a browser), choosing a doc can sometimes pop open the doc in a window, leaving the menu page with a spinner that never cancels.

Comment 3 by ortuno@chromium.org, Sep 26 2017

Status: WontFix (was: Available)
Closing for now, but we could revisit if devs complain about their app not opening.

Yeah :( (At least the docs case should be fixed in the latest dev since it's a same origin navigation).

Sign in to add a comment