Repository navigation
Design scoped effects and stronger host compatibility #13
Description
P2 follow-up; investigate real integration cases before expanding the API.
- Evaluate explicit effect scopes, strict CSP support and fixed-descendant filter alternatives.
- Decide whether Shadow DOM support is viable; document iframe boundaries.
- Specify compatible defaults and migration impact before implementation.
- Verify scopes, reset/unmount restoration and widget exclusion in packed browser consumers.
Acceptance: source-grounded design and independently verified supported cases, without universal-host claims.
References: roadmap, development/acceptance guide.
Activity
Merge pull request #178 from prabothcharith/feat/issue-13-scoped-effe…
prabothcharith commentedon Nov 4, 2026
Resolved and verified in PR #178 (merged into development). Added effectScope container targeting prop (CSS selector, HTMLElement, or React ref), fixed-descendant filter isolation, open Shadow DOM traversal, and strict CSP nonce support (nonce prop). Documented in docs/SCOPED_EFFECTS.md.