Provide a TAO-bypass for Navigation timing
Open
Nobody has claimed this yet.
Clarification
editorial
hackathon_15_09_20
hackathon_2020
requires Fetch integration
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Navigation Timing is sharing many attribute definitions with Resource Timing, but doesn't use TAO, as it makes no sense in NT's context. We need to provide an internal flag that enables NT to reuse those definitions without requiring TAO. See https://github.com/w3c/navigation-timing/issues/117
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 by reviewing the shared attribute definitions in the Resource Timing specification and the related Navigation Timing issue 117. Determine where Navigation Timing needs to reuse those definitions without TAO enforcement; done means the specifications support that reuse through an internal mechanism.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100