`InitiatorType` should not single out XHR
Open
Nobody has claimed this yet.
Clarification
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Talking to @annevk on WHATWG IRC, it doesn't make sense for initiatorType processing to single out XHR.
Unless there are webcompat issues with deprecating and removing that, it should be folded into the fetch initiator type.
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 current Resource Timing specification language for initiatorType and the issue discussion, then investigate whether removing the special XHR handling has web-compat implications. Done means the specification consistently folds XHR into the fetch initiator type, with any compatibility concern resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100