[Internal] [P-Preview1] Request: add option to skip in-app-web browsing of chrome-tab, to go directly to Chrome |
||||
Issue descriptionFiling this issue from buganizer - b/77619888 Android P developer has requested to add option to skip in-app-web browsing of chrome-tab, to go directly to Chrome. Description provided by external developer: ============================================ It's always nicer to have a full fledged web browsing experience, when you visit a webpage from within an app. And it seems I'm not the only one: https://thenextweb.com/opinion/2018/04/03/rant-app-browsers-annoying-mostly-useless/ Please add an option to enable, so that we will skip this phase, and go directly to Chrome instead. * What is the desired behavior of the feature? (Be specific!) To have an option in the settings, to always skip in-app web browsing, and go directly to the web browser instead. * If relevant, why are current approaches or workarounds insufficient? Requires 2 additional steps, and only then you get the full experience of a web browser. * If relevant, what new use cases will this feature will enable? Less steps, more features of a full fledged web browser. ============================================ This seems to feature request from above comment. Leaving the issue as Untriaged for further input's on this issue. Thanks!
,
Jul 30
,
Jul 30
Sounds like a reasonable feature request. We just need to think about where that global opt-out would live and any current experiences that would be negatively affected. Our plate is full currently though. I don't think M70 is a target but I'm not familiar with Clank's triaging process so feel free to update those labels.
,
Jul 30
,
Jul 30
yes please. Or at least an option that first navigation gets me into full chrome
,
Jul 30
Yeah, if you can find a place in Settings to put this option, implementing it probably wouldn't be hard…
,
Jul 30
Just to add what we have considered in the past: This was also raised previously, and like mardini@ mentioned, finding where the global opt out would live was a challenge (since custom tabs is a platform feature, the question here is : "Is the opt out at device level to all browser implementations, or browser specific, or specific to a client from a browser"). Note that, especially through multiple Chrome channels, the issue of "browser specific vs all browsers" is something that needs to be addressed. One thing we had considered, but haven't gotten to was to trigger an opt out dialog for users who seem to use "Open in browser" menu item frequently, so that we don't have to assume if we put an opt out somewhere, everyone will know where it is and how to use it.
,
Jul 30
I would definitely consider a CCT opt-out a Chrome feature, not a platform feature – it turns that particular browser into one that degrades gracefully when handling custom tab intents. Other browsers can handle custom tabs in whichever way they choose. The opt out is nice, but then would we have no option of opting in again? Otherwise this boils down to the same question of where to put the setting.
,
Aug 2
I think making a CCT opt-out available in Chrome Settings (as opposed to a global opt-out) would satisfy the needs of most of our users given our current CCT usage distribution. If the user has a different default browser, then this should have no effect. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tedc...@chromium.org
, Jul 30Components: -UI>Browser UI>Browser>Mobile>CustomTabs