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.
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
-
-
...and there are multiple ways of achieveing that. They could, for instance, embed a web engine of their own design (or take another one off the shelf). Or they could do the work to hook up the various APIs they've left unimplemented in their "browser".
-
All of that is strictly better than status-quo. FB has picked the worst of all these: they neither invest enough in their "browsr" to not break the web, nor participate as good citizens in the system to avoid undermining user choice.
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
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.
- 3 more replies
-
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.