Skip to content

wasm-unsafe-eval support #260

@antonok-edm

Description

@antonok-edm

When salvation encounters a Content Security Policy with the wasm-unsafe-eval directive, it reports:

Bad content security policy: Expecting source-expression but found "'wasm-unsafe-eval'".

According to https://caniuse.com/?search=wasm-unsafe-eval, wasm-unsafe-eval is supported by 87.81% of all users globally, which is quite broad and it's probably reasonable to count it as a valid directive now.

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