Right! I know how much @slightlylate (and I) love URLs. I’m reading back over what I wrote trying to find any implication otherwise.
-
-
Replying to @adactio
: you can start with "not bothering to ask if the lack of URL bar access is intended/permanent". You can DM me any time, yano
2 replies 0 retweets 0 likes -
Replying to @slightlylate @adactio
: but nope. No curiosity, only aspersion and judgement.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Judgement on the decision, not on individuals. There’s a difference (though I understand there are people behind any decision)
2 replies 0 retweets 1 like -
Replying to @adactio
: ...without bothering to find out if decision is being taken in a context that would dampen your "Chrome team hates URLs" narrative
1 reply 0 retweets 0 likes -
Replying to @slightlylate
I'm very sorry I upset you, Alex. I stand by my criticism of the decision to mandate standalone/fullscreen display values.
2 replies 0 retweets 0 likes -
Replying to @adactio
: yeaaaah, and now that you've been informed that there will be UI that gets you back to a URL bar regardless...?
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Until that ships, the *current* situation is very bad for URLs. If that shipped first, it would be a different situation.
1 reply 0 retweets 0 likes -
Replying to @adactio
: yep, there we go. Why let inconvenient data ruin a narrative? Classic.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Saying “we’ll do something later” isn’t data. Why not do something first, *then* remove the prompt for display:browser?
1 reply 1 retweet 1 like
: a great question! One you didn't ask. Clearly a mistake. One I own.
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.