So that's a concern about the behavior of In-App-Browser UI and the attribution therein, not about intents out to the user's *actual* browser?
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @sayrer
That's not true *at all* FB has multiple options here that will get us to a situation where they are not *simultaneously* undermining the web platform & user choice. They could pick just one! Or zero!
1 reply 0 retweets 0 likes -
Replying to @slightlylate @sayrer
Remember the counterfactual: unless you break it, tapping on a link in Android *takes the user to their browser*. That runs zero of these risks. Alternatively, if FB wanted to continue to undermine user choice but not break the web, they could fix their godforsaken IAB's impl
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer
I've, multiple times, outlined many ways that FB can avoid CCT if they think the same. They can *just send the user to their browser*, as the system defaults to. Or fix their "browser". Nothing about CCT strictly speaking needs to improve here. Ball's in FB's court.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
CCT is a protocol. What receivers do is out of the hands of senders.
-
This Tweet is unavailable.
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.