Chrome Version: 72
OS: All desktop

What steps will reproduce the problem?
(1) Go to any (non-PWA) website, e.g. http://example.com.
(2) Chrome menu -> More tools -> Create shortcut.
(3) (Chrome OS) find app in launcher / (other OS) find app in chrome:apps.
(4) Right-click -> Open as window
(5) Relaunch app.

What is the expected result?
App acts like a PWA in most respects.

In particular:
- Links in browser to this app show "Open in <app>" for this app.
- Browser three-dot-menu "open in app" should work.
- Notifications open in the app window.
- Chrome OS: Intent picker shows up when navigating to the scope.
- If it's "http" then it shows a location bar at all times [security].

However:
- We have to figure out whether we'll distinguish mixed content (in a PWA, mixed content is blocked, we can't really do that for a non-PWA).
- We wouldn't expect the apps to work offline or have a proper title bar / icon.
- We would not show the "Install" button for non-PWAs on the Chrome menu.

What happens instead?
The above things don't work. We originally set this deliberately, but it's become too hard to manage. By making them behave the same, we can remove a lot of code complexity.

Note: Essentially, all we have to do here is create a "scope" for a bookmark app. The scope should be, roughly, the document URL, minus the query and fragment, minus the last part of the filename. (e.g., "http://example.com/foo/bar?baz=boz" -> "http://example.com/foo/"). [Subject to discussion.]

Note: This will allow us to more easily associate a page with a bookmark app, so soft-blocking  Issue 907353 .