They don't and that's not OK. But more to the point, giving a choice will not fix the problem in practice. This is a serious design flaw that users shouldn't need to know or care about.
-
-
Replying to @KenjiBaheux @tobie and
It would be great if more in-app browsers (or even all of them) could be the good kind. Tough problem to take away or restrict existing APIs, but worth it to work on it. In any case, the in-app browsers that are implemented the less good way are still browsers.
1 reply 0 retweets 1 like -
Replying to @othermaciej @KenjiBaheux and
I've been defining browsers as "apps that accept all navigation intents"; that's a bit Android specific (as you can actually replace the default browser there), but it captures the essential difference in responsibility to the user, IMO. These WebView things are franken-browsers.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @othermaciej and
Arriving at a sort of agreed-upon definition would be interesting and would help inform conversations. Maybe a
@w3ctag finding? How can we make progress when there's no agreement between browser engineers as towards what we're working?2 replies 0 retweets 2 likes -
Replying to @tobie @slightlylate and
I’m not sure a TAG finding on “what is a browser” would be of practical use, and it could easily fly off into the abstraction stratosphere. (My quaint view is: if it does web browsing, it’s a web browser. But not sure this has anu practical relevance.)
2 replies 0 retweets 2 likes -
Replying to @othermaciej @slightlylate and
Does browsing imply being able to type your own URLs?
1 reply 0 retweets 1 like -
Replying to @tobie @othermaciej and
or having trusted UI indicating what the URL (or at least origin) is?
1 reply 0 retweets 0 likes -
Replying to @davidbaron @tobie and
Rather than abstract questions about where Web browsers end and start, I think it would be interesting to document the risks or harms that are created by exposing Web content outside of usual Web browser UI expectations, and see where and how they could be mitigated
4 replies 2 retweets 6 likes -
Replying to @dontcallmeDOM @davidbaron and
That would be more useful. The most common issue is privacy: the app observes your browsing or add additional tracking info for websites. Primary browsers can do this too of course. Users have choice and should know that using, say, Chrome is a privacy risk. But do they?
2 replies 0 retweets 3 likes -
Replying to @othermaciej @dontcallmeDOM and1 reply 0 retweets 1 like
Apple policy commentary aside, there's a user-study in here somewhere (that would need to be conducted on Desktop, CrOS, or Android) about why users switch browsers.
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.