- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 19 Oct 2020 08:22:43 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 October 2020 15:22:56 UTC
> shift the document-domain feature policy's allowlist from * to 'none'.
Where did document-domain end up in the feature policy -> { permissions policy, document policy } split? It seems like one of those two would be more suitable for this sort of thing, but I'm never sure which one... /cc @clelland @annevk.
> After more usage disappears in step 2, remove the setter entirely.
There are other options which could be slightly less breaking, e.g. making the setter a no-op via `[LegacyLenientSetter]`, or using `[Replaceable]`. Removing it entirely would be the most clean, though!
--
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-712241396
Received on Monday, 19 October 2020 15:22:56 UTC