It might be time for gopher to go ... what do you say @mikewest? 895041
-
-
Replying to @nasko
I think it’s a good idea! See https://github.com/whatwg/url/issues/342 … (and I have a year-old patch lying around somewhere).
@annevk wasn’t thrilled with the idea of changing the parser behavior, and I ran out of bandwidth to continue the conversation.1 reply 0 retweets 0 likes -
Yes, I found it and started a new version of it due to the changes that have happened since. Thanks for the pointer to the discussion, I wasn't aware we are keen on keeping it around. Filed a bug in our tracker earlier if folks want to comment - https://bugs.chromium.org/p/chromium/issues/detail?id=895041 ….
1 reply 0 retweets 0 likes -
It’s still unclear to me why it’s worth breaking parser stability for this. I’d much rather have Chrome invest in aligning with the
@urlstandard rather than diverge further.1 reply 0 retweets 0 likes -
To what end? Better gopher support? More security bugs? Specs follow implementer trajectory for a reason.
2 replies 0 retweets 0 likes
Compat matters *when compat matters*. Does it matter here? Are there other concerns that prempt compat?
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.