Draft
Conversation
Contributor
|
Cool stuff! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Example of using the performance api to measure event-handling timings. These can be nicely viewed in devtools
Performancetab profiles. In the example below, we see thedoc/txevent taking the majority of time spent in thekeypressevent (these timings are shown in the upper section, while the call stack is shown at the bottom):This PR is not production-ready - that would require an ability to turn this on/off, and ensure that the apis are available in the browser before using them, as well as further thought as to what exactly we should be measuring.