add NoScript to list of extensions known to cause issues
@shekhar4704 is already working on this.
Since Oct 11, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
The payload does not name the page that lists problem extensions, so first search the repository for an existing entry such as another blocker or privacy extension to find that list. Add NoScript in the same format, with a short note on the problem it causes for CryptPad. Done when NoScript appears in that list and the Sphinx docs still build.
Written by the indexing model from the issue text.
Description
From a report in our chat, but obvious since anything made to interfere with JavaScript could have an effect on CryptPad.
- Dominant language
- HTML
- Stars
- 39
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cryptpad/documentation
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
cryptpad/documentation#161 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cryptpad/documentation#159 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
cryptpad/documentation#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cryptpad/documentation#155 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
cryptpad/documentation#154 · 1 assignee ·
All issues in cryptpad/documentation
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Nemotron section 4 never says which reasoning_effort values the family takes, and only `high` returns a tracePossibly taken @sample-per-model-bedrock-dev-agent claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws-samples/sample-per-model-bedrock#207 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
restatedev/docs-restate#422 ·
Maintainers usually reply within 2 days