- From: Anne van Kesteren via GitHub <noreply@w3.org>
- Date: Wed, 08 Apr 2026 14:39:30 +0000
- To: public-css-archive@w3.org
I don't think WebExtensions are a valid use case here, but they also could set headers I think if provided with the right API. And the first such `<meta>` is an extremely fragile setup that's definitely considered a mutable policy as you start out without a policy and if you find such a `<meta>` element you have one. But there's absolutely no guarantee when you might find that `<meta>` element. This has been hugely problematic for `<meta charset>` for instance and that's still not interoperable today. Adding to that problem does not seem good. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1771#issuecomment-4207081228 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 April 2026 14:39:31 UTC