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

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

This may not be true in the cross-origin case -- Permissions policy will also necessarily silently opt in cross-origin frames as well, with no action required from a third party.

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

👍 


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