The client is OSS & under developer control: https://github.com/GoogleChrome/custom-tabs-client … What browsers collect when you invoke them is what browsers collect when you invoke them.
-
-
This Tweet is unavailable.
-
Replying to @sayrer
WebView API is here: https://developer.android.com/reference/android/webkit/WebView … Metrics opt-out is but a google search away:https://developer.android.com/guide/webapps/managing-webview#metrics …
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer
No, you're *invoking the user's browser to navigate on their behalf*. The honest thing would just be to intent out, but FB doesn't do that...so here we are.
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer
So intent out. Do the honest thing and stop subverting user clicks to the web. Stop dressing it up in your app's UI. Show them what's happening.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer
That's a great feature request. Something one could imagine us doing. That said, the onus is on FB to fix this, probably by intenting out to browser until they get their house in order and make a list of required features available for discussion.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @sayrer
Again, this can't be stressed enough: FB broke this, not the system or browsers. It's not necessarily on them to fix it for FB.
1 reply 0 retweets 0 likes
There are lots of ways they could: 1.) staff a real browser team, bring impl up to par 2.) intent out to a real browser 3.) CCT Doing none of the above (current state) is just abuse of the user & the ecosystem.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.