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

mikewest left a comment (whatwg/url#288)

> @jasnell maybe. @mikewest is exploring some ideas around exposing origin or site, and some of the ideas around public suffix and registrable domains overlap. Not sure about IP addresses vs domains though. https://github.com/mikewest/origin-api

Regardless of where the `Origin` discussion goes:

1.  It seems reasonable to me to create some kind of exposure for questions around IP addresses. I don't think that distinction is particularly relevant in the context of the `Origin` proposal (which intentionally hides details like scheme, host, and port behind high-level comparison methods), but could fit well into something like the `URLHost` proposal here.

2.  It also seems pretty reasonable to expose a user agent's understanding of the PSL somewhere in the context of `URL`. I could imagine doing that a few ways, via `isSameSite()`/`isSchemelesslySameSite()` methods, `registrableDomain` getters, etc.

> Not quite sure what to make of that yet, especially with "partition" (for lack of a better word) becoming the security boundary for state in browsers.

Perhaps we should try to piece together what that thing might look like? As I mentioned in https://github.com/WebKit/standards-positions/issues/538#issuecomment-3195415631, my feeling is that it would be something that held an `Origin` along with other bits and pieces, but I could imagine other representations.

> The other thing that concerns me a little bit is that I've learned that WebRTC wants something like this but for host + port. And so I've wondered if not addressing port is problematic.

Do you have a pointer to that discussion? I'd like to understand the use case.

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

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