Document PerformanceEventTiming members #21551
Merged
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 documents the
PerformanceEventTiming
API members.Motivation
openwebdocs/project#62
Additional details
I think very often it is hard to come up with good and sensible content for property pages. In fact, I think many MDN API property pages are thin. I tried to provide examples here for everything, though. I hope it doesn't look all too constructed. I think it just tells that I sometimes don't exactly know the precise use case for a property. If you have better use cases or ideas, let me know and I'm happy to make the example code better.
Related issues and pull requests
#21531 is the PR that updates the
PerformanceEventTiming
interface page. @wbamberg is reviewing it and it might be nice to get his review on this one as well but I won't require it :)