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

Link Resource Timing entry #2

Open
npm1 opened this issue Mar 18, 2019 · 3 comments
Open

Link Resource Timing entry #2

npm1 opened this issue Mar 18, 2019 · 3 comments

Comments

@npm1
Copy link
Collaborator

npm1 commented Mar 18, 2019

Currently, the Element Timing API exposes only two of the attributes from Resource Timing: responseEnd and name. For images, it seems useful to instead provide a direct link to the Resource Timing entry corresponding to the element. For text, we will not be able to provide this at first, and in fact text elements may not correspond to any Resource Timing entry. But overall it seems useful to provide a pointer to RT from ET.

This issue is filed based on the discussion at w3c/user-timing#17.

@sergeychernyshev
Copy link

Text might enjoy a link to a custom font resource used to render it.

@npm1
Copy link
Collaborator Author

npm1 commented Mar 19, 2019

Correct! I mention that we might not be able to provide this at first because on our text proposal we do not wait until webfonts have loaded. In the future, we could, but text is also a bit trickier because a single block of text (like a paragraph) could be using multiple webfonts (so we'd need an array of RT entries).

@sergeychernyshev
Copy link

Agreed. Just wanted to weigh in as I see that being important quite often and requires some attention when we use User Timing for this.

Good point about multiple web fonts - not sure how this will handle font-display: swap situation though... we currently measure it anyway knowing that there is a difference in experience between browsers that support it and browsers that don't. Same applies to other values, I assume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants