Update PerformanceResourceTiming.initiatorType #22539
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Preview URLs (this comment was updated 2022-11-26 09:57:07.698076) |
files/en-us/web/api/performanceresourcetiming/initiatortype/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/performanceresourcetiming/initiatortype/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/performanceresourcetiming/initiatortype/index.md
Outdated
Show resolved
Hide resolved
files/en-us/web/api/performanceresourcetiming/initiatortype/index.md
Outdated
Show resolved
Hide resolved
sideshowbarker
approved these changes
Nov 26, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/initiatorType with the goal to provide a better list of possible values and more practical example code.
Motivation
openwebdocs/project#62
Additional details
Finding out which values are actually possible (spec'ed and observed in the wild) was quite tricky and lead me into a bit of a rabbit hole today. I filed w3c/resource-timing#364 with the specification. Depending on an answer there, this PR might need more tweaks.