Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome 133 returns LCP and Element Timing renderTime for cross-origin media #25735

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tunetheweb
Copy link
Contributor

@tunetheweb tunetheweb commented Jan 21, 2025

Summary

There have been some recent changes to renderTime for LCP and Element Timing and Chrome is changing this for Chrome 133.

Test results and supporting details

See also:

Related issues

mdn/content#37743

@github-actions github-actions bot added data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:m [PR only] 25-100 LoC changed labels Jan 21, 2025
{
"version_added": "77",
"partial_implementation": true,
"notes": "Returns 0 for cross-origin media."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whenever we have multiple browsers with the same notes, I feel like it would be better to add a behavioral subfeature for it.

@Elchi3 Wdyt?

@caugner caugner changed the title Update renderTime for LCP and Element Timing Chrome 133 returns LCP and Element Timing renderTime for cross-origin media Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:m [PR only] 25-100 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants