Re: [w3ctag/design-reviews] Deprecating `document.domain`. (#564)

Given that the suggestion is to turn it off by default, the core distinction seems to be whether the top-level can opt all its dependencies in, or whether the dependencies need to opt themselves in. The former is probably easier to deploy, but if developers already have to touch top-level pages, asking them to also touch nested pages doesn't seem like a huge additional burden.

That's a long way of saying that I'm comfortable with whichever philosophical position on `document-domain` y'all end up taking, and will adjust the proposal's recommendation for an opt-in accordingly. It says `feature-policy` right now only because that's what currently works in Chromium. :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/564#issuecomment-712293189