Chrome 133 returns LCP and Element Timing renderTime for cross-origin media #25735
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
github-actions
bot
added
data:api
caugner
reviewed
Jan 24, 2025
caugner
changed the title
caugner
requested changes
Jan 28, 2025
caugner
requested changes
Jan 30, 2025
Co-authored-by: Claas Augner <[email protected]>
tunetheweb
commented
Jan 30, 2025
caugner
requested changes
Feb 5, 2025
Co-authored-by: Claas Augner <[email protected]>
Co-authored-by: Claas Augner <[email protected]>
tunetheweb
commented
Feb 5, 2025
caugner
approved these changes
Feb 7, 2025
Merged
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.
Summary
There have been some recent changes to
renderTimefor LCP and Element Timing and Chrome is changing this for Chrome 133.Test results and supporting details
See also:
Related issues
mdn/content#37743