core: use performance.now in isolation
#14685
Merged
Conversation
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
| /** @type {Promise<void>} */ | ||
| const promise = new Promise((resolve, reject) => { | ||
| executionContext.evaluate(registerPerformanceObserverInPage, {args: []}) | ||
| executionContext.evaluate(registerPerformanceObserverInPage, {args: [], useIsolation: true}) |
Contributor
There was a problem hiding this comment.
Interesting! I don't have any intuition for PerformanceObserver behavior in an isolated context. What happens?
Contributor
Author
There was a problem hiding this comment.
From my testing, it works the same. We still get the longtask events.
connorjclark
approved these changes
Jan 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Fixes #14303
Related #14003