feat: Add conditional marker exposure based on cross-origin isolation #85
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
|
@arturjanc @ArthurSonzogni I am trying to do a modification on the JS Self Profiler API. Could you help me with any feedback that you could provide? |
|
Thanks! Looping in +@camillelamy as I’m currently on paternity leave and won’t be able to reply confidently immediately from what I recall. This feature dates back to ~4 years ago: here is the previous discussion. |
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.
feat: Add conditional marker exposure based on cross-origin isolation
Enable selective marker disclosure based on security context:
This allows access to layout/style timing (already available via DOM APIs)
in regular contexts while protecting sensitive timing information.
Maintains full backward compatibility with existing API surface.
Preview | Diff