Issue metadata
Sign in to add a comment
|
Show URL bar when WebAPK navigates outside of WebAPK scope |
||||||||||||||||||||||||
Issue descriptionIf the WebAPK navigates to an out-of-scope URL when it is in the background, the navigation will not be delegated to Chrome Currently, the URL bar is displayed when a navigation takes the user to a different domain (WebappActivity#shouldShowTopControls()). However the WebAPK scope may be a subdomain e.g. www.google.com/maps If the WebAPK scope is www.google.com/maps a background navigation from www.google.com/maps to www.google.com/flights should show the URL bar. Currently the WebAPK does not show the URL bar
,
May 25 2016
I don't think we should ever show the URL bar. A navigation which leaves the scope (or even sw registration scope) should bounce out to chrome. The background scenario is unlikely but I suppose it could happen. That would cause chrome to come to the foreground so I'm not really sure. +owen for thoughts Re: #1 - yes, any navigation out of scope should leave the webapk
,
Jun 30 2016
,
Jul 7 2016
I recant answer in #2. There are edge cases where we'd have to show it. We've also debated that "intent-in" and "remain-in" may be different so it's possible this would show in edge cases. Note this currently only shows if the host is different, but a scope smaller than a origin won't display it (WebappDelegateFactory.shouldShowTopControls) We may also want better treatment for this, possibly along the lines of issue 624788
,
Jul 18 2016
,
Jul 25 2016
Going to dup this against issue 624236 . We should use CCT presentation when outside webapk scope |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pkotw...@chromium.org
, May 24 2016