Sam mentioned that the tone may have softened on this. Can you follow-up?

Discussed at the weekly 7/19. Proposal is to follow the existing behavior for standalone (no UI so long as you're on the origin regardless of SW, show the minibar or CCT for other origins, only open Chrome with window.open)

Grace suggested that it might be as easy to directly open a CCT as to switch to using the minibar. We were planning to inherit this behavior when it changed in WebAppActivity but if it's just as easy to change now we should UI-review the CCT plan and then implement that instead.

(yfriedman@ to investigate or delegate whether it's as straightforward as suspected.)

It is our intention that opening external links in non-WebAPK webapps will open a CCT on top of the app frame, so doing this in WebAPKs would be consistent.

https://codereview.chromium.org/2173433002 is a hacked-up prototype (just did the minimal thing to make it work but may have edge-cases)

Also attached a video - assuming that's what we want, I can clean it up and mail for review.

Deleted: cct.mp4 5.4 MB

	cct.mp4 5.4 MB View Download

Note this doesn't work if the link is meant to open in a new window "_target=blank". Not sure if that's feasible yet

 Issue 614519  has been merged into this issue.

This bug is all yours. I know that you are working on product excellence stuff right now. This bug is not very urgent. Its just so that you have something to work on if you're done everything else