I don't like the idea that third party can link to anything they like here. Also since this is a not a consistent pattern, I wouldn't recommend keeping it.
@Peter, unless you feel strongly against it, let's remove it from CrOS (and of course from the dev site)
Sorry for missing this!
I don't have particularly strong feelings on whether to keep this. Let me check if there's UMA indicating how often this gets used, which could be a data point in our decision.
Sebastien, I guess we could see this as being analogous to what Android does. For example, navigate to:
Settings
> Apps & notifications
> Chrome
> App notifications
> Additional settings in app
This used to be a gear in the page's header prior to Android O. A quick check tells me that most 1P and many large 3P apps include this toggle.
Finally, removal from Chrome OS here means complete removal of the API.
According to UMA, we've fired this event ~3.5k times for ~1.3k users on Chrome OS in the past 28 days. Even when compensating for users who aren't opted in to UMA those remain very small numbers.
https://uma.googleplex.com/p/chrome/usage/?sid=402033bc4c61ad1c773b3b35915d16d8
Also, let's make this public - any potential changes to our API surface shouldn't be R-V-G :).
Comment 1 by tetsui@chromium.org
, Nov 6 2017Labels: Restrict-View-Google
35.9 KB
35.9 KB View Download