Re: [whatwg/url] Expose a URLHost class to JavaScript (#288)

mikewest left a comment (whatwg/url#288)

> See step 4 of https://w3c.github.io/webrtc-pc/#dfn-validate-an-ice-server-url. (Some discussion in https://bugs.webkit.org/show_bug.cgi?id=164508 and [w3c/webrtc-pc#2660](https://github.com/w3c/webrtc-pc/issues/2660).)

Thanks. I agree that something cleaner than step 4 of https://w3c.github.io/webrtc-pc/#dfn-validate-an-ice-server-url would be nice to have, though I wonder how much of a one-off it would end up being.

For STUN and TURN specifically, the prevalence of those particular protocols might justify baking a scheme-specific parsing rule into URL more directly, such that `new URL("stun:server.goes.here:1234")` results in a URL object with a host and port. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/288#issuecomment-3351010350
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/pull/288/c3351010350@github.com>