Skip to content

Test/Demo with strict content security policy #1431

@alexbrasetvik

Description

@alexbrasetvik

Consumers of EUI, such as Cloud's UI, use (or plan to use) a strict content security policy. "strict" means no "unsafe-inline" or "unsafe-eval".

If EUI has one, that can help make sure all the components of EUI are compatible with this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationIssues or PRs that only affect documentation - will not need changelog entriesstale-issue(Don't delete - used for automation)stale-issue-closed(Don't delete - used for automation)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions