Deprecate DOMInjector in favor of CSSOMInjector
Open
enhancement
- Dominant language
- TypeScript
- Stars
- 624
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
As browsers are [adding support for debugging the CSSOM](https://developers.google.com/web/updates/2020/06/devtools), there should be no need to resort to slower DOM-based solutions.
Contributor guide
Research direction
Start by locating the DOMInjector and CSSOMInjector entry points in the TypeScript codebase and comparing their usage. Confirm which callers and public APIs depend on DOMInjector, then define completion as moving those uses toward CSSOMInjector while preserving the runtime behavior described by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100