Skip to content

Document-Isolation-Policy Header via meta tag #3

Open

Description

@weizman

How do we feel about this one? Asking from the following perspectives:

  • Are there firm reasons (security/design) to forbid that?
  • Is it even feasible implementation-wise? Would it make things significantly harder/more complex?

Just like CSP, features like COOP/COEP and also DIP are very useful, and web extensions should be able to make use of them too. In order to get there, we must either implement explicit support (such as CSP in manifest.json), or allow setting such headers via the meta#http-equiv tag.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions