Installed PWAs from NTP should launch in right container |
||
Issue descriptionChrome Version: (copy from chrome://version) OS: Chrome OS What steps will reproduce the problem? (1) install a desktop PWA and set it to launch in a window (2) use it a lot so it appears in the NTP (3) launch it from the NTP What is the expected result? - it should launch in a window What happens instead? - it launches in a tab Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jun 18 2018
I think this falls under link capturing, which we've turned off for now, but will eventually bring back with launch event (where launching from the NTP will be considered a `launch`). For now, I think it makes the most sense to just think of these as normal navigations, though I can imagine disagreement.
,
Jun 18 2018
I guess technically it is link capturing, but I think of the NTP as a launch surface very similar to chrome://apps, the shelf, the app list etc. |
||
►
Sign in to add a comment |
||
Comment 1 by benwells@chromium.org
, Jun 18 2018