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

>Why would you need to, though? 

Well, my *personal* immediate need was responding to an enterprise who asked "Hey, we have a page at deeply.nested.fuzzle.bunnies.io and we'd like to understand where we have to host a subresource such that it's not considered Same Site to us. Help." To answer that question, I could go manually look through the current public WebPageTest list and then for completeness go look through all of the changelog to see whether it might've possibly changed between the browser build they are using and the current version. That's super-cumbersome.

Another possible use case (which I suspect you might not be happy about) is the best practice documented in [Guidelines for URLDisplay](https://chromium.googlesource.com/chromium/src/+/master/docs/security/url_display_guidelines/url_display_guidelines.md#:~:text=%20Guidelines%20for%20URL%20Display%20%201%20Background.,make%20one...%204%20Further%20Reading.%20%20More%20), which calls for ensuring that the Registrable Domain portion of a URL is always visible. For a web application to implement that Best Practice requires knowing the registrable domain.

-- 
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-676498407