Add Event Timing info to PerformanceEntry pages #21555
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
Flaws (2)Note! 4 documents with no flaws that don't need to be listed. 🎉 URL:
|
sideshowbarker
approved these changes
Oct 16, 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 adds information from the Event Timing API (
PerformanceEventTiming) to its parentPerformanceEntry.Motivation
openwebdocs/project#62
Additional details
I think we want to take a closer look at the
PerformanceEntrypages at a later stage. It seems it is an abstract interface for many performance APIs and we should see how to improve these pages. This PR just adds to what the current structures offer.Related issues and pull requests
#21531 documents these properties in a "Instance properties" section as well.