Evaluate removing the Shadow DOM
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
### Summary
Evaluate removing the Shadow DOM in all components across ICDS.
### 💬 Description
Investigate the feasibility of dropping Shadow DOM usage in our components.
- Pick one component.
- Explore whether scoped styles alone can provide the necessary encapsulation benefits. Assess potential drawbacks, test in consuming apps, and ensure features like slots still function correctly. Consider testing the component inside the test app or at least alongside/within other components
- Document on this ticket any issues or quirks you noticed.
- Estimate the effort required to migrate all components - identified by Spike subissue.
### 💰 Use value
This spike aims to address recurring issues caused by Shadow DOM issues.
Contributor guide
Research direction
Pick one component from the ICDS component set and test it in the test app or alongside other components without Shadow DOM. Check scoped-style encapsulation, consuming-app behavior, and slot functionality; document observed quirks and estimate the effort to migrate all components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100