Include nonce attribute for Content Security Policy

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend, security

Research direction

Review the linked enhance-starter-project issue and the CSP error shown here to understand when a nonce is available and which form elements need it. Locate the form-element rendering code and its existing tests, then verify that nonce-bearing output includes the nonce attribute without changing output when no nonce is available.

Written by the indexing model from the issue text.

Description

See https://github.com/enhance-dev/enhance-starter-project/issues/12

When a nonce is available, form-elements should include that nonce as an attribute to prevent errors like in this screenshot:
image

Refused to apply inline style because it violates the following Content Security Policy directive: "[omitted for brevity]". Either the 'unsafe-inline' keyword, a hash ('sha256-WZ567ntT3BKIFaeoTtOOEdkkOJR5UidQJ809ufOE0zk='), or a nonce ('nonce-...') is required to enable inline execution.

Dominant language
JavaScript
Stars
4
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.