How to set a nested strategy
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
Currently there's no straight forward way to set a nested strategy for ContainerTiming as the PerformanceObserver doesn't accept options. This may need to be a new field on PerformanceObserverInit
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PerformanceObserver and PerformanceObserverInit definitions in the linked Performance Timeline specification. Determine how a nested ContainerTiming strategy should be represented within the observer options model. Done means the design question is resolved and the required specification change is clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100