Note that responsible native apps *have* a way of creating an "in app browser" that doesn't subvert user choice or break the web: https://developer.chrome.com/multidevice/android/customtabs … Any browser can implement the protocol & default browser will be used. FB can enable this with their next update.https://twitter.com/slightlylate/status/1167548118876901376 …
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.
-
-
This Tweet is unavailable.
-
This perspective is super confusing. Do you think that apps, as a general matter, should not send links to user's default browser?
- 9 more replies
-
-
-
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.
-
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.
End of conversation
New conversation -
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.