Thanks for helping make WebMeld smaller, safer, and more useful.
- Search existing issues first.
- Reproduce bugs on a public or synthetic page when possible.
- Never paste API keys, private HTML, personal data, or authenticated page screenshots into an issue.
- For security concerns, follow SECURITY.md.
- Fork and clone the repository.
- Open
chrome://extensions. - Enable Developer mode and load the repository as an unpacked extension.
- After changing extension code, click Reload on the extension card and refresh the test page.
- Run the checks:
npm run checkNo production dependency or build step is required.
Keep changes focused. A good pull request explains:
- the user problem;
- the chosen behavior and trade-offs;
- how the change was verified on a real page;
- whether it changes permissions, transmitted data, or stored data.
Any change that expands model output beyond constrained CSS declarations requires an explicit security design discussion first.
- Prefer plain browser APIs and readable ES2020-compatible JavaScript.
- Keep model output untrusted at every boundary.
- Preserve preview, verification, rollback, and local-first behavior.
- Avoid adding dependencies for behavior that is clear in a few lines of platform code.