-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Chrome blocks extensions on browser-internal pages, the Chrome Web Store, and some protected surfaces. Open a normal HTTP or HTTPS page and try again.
- Confirm Elements is not paused for the site.
- Check whether the page URL still matches the saved site.
- Open Options and confirm the rule still exists and is enabled.
- The site's DOM may have changed enough that the saved selector no longer identifies the intended element; recreate the rule if necessary.
Elements sanitizes custom CSS before storing or applying it. Remove unsafe or unsupported constructs instead of weakening the sanitizer.
Use a JSON export created by Elements and keep its schema intact. Invalid imports are rejected before replacing current rules. Preserve the original export until the import succeeds.
Use Node.js 22 and run:
npm ci
npm run validate
npm run build:chrome
npm run verify:buildFor deeper setup and test details, read the repository troubleshooting guide.
Use synthetic page content and remove private URLs, rules, imported backups, and browsing details. Report suspected vulnerabilities through GitHub private vulnerability reporting, not a public issue.