Re: [whatwg/url] Feature proposal: eTLD+1 web API (#528)

@achristensen07 One very obvious use-case is the same one currently used in browser address bars: to highlight the eTLD+1 in UIs. [This page](https://transcend.io/consent-manager/) could embolden the eTLD+1 of shown domains so that users can more easily see the important part of the domain.

CSP generation optimization use-case: I'm working on a synchronous blocking JavaScript library that regulates client-side network emissions and generates dynamic Content Security Policies based on user tracking consent. The library that I'm working on is currently not eTLD+1-aware due to the PSL size requirement. If it could be eTLD+1-aware, I could generate more-concise CSPs.

Iterative hostname matching use-case: eTLD+1-aware hostname matching algorithms can skip comparison iterations on eTLD+1 hostname parts.

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