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

Broken references in Event Timing API #137

Open
1 task
dontcallmedom-bot opened this issue Jan 24, 2024 · 2 comments
Open
1 task

Broken references in Event Timing API #137

dontcallmedom-bot opened this issue Jan 24, 2024 · 2 comments
Assignees

Comments

@dontcallmedom-bot
Copy link

While crawling Event Timing API, the following links to other specifications were detected as pointing to non-existing anchors:

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

@mmocny
Copy link
Contributor

mmocny commented Aug 19, 2024

This was removed as part of the Element Timing -> Paint Timing / LCP refactor (See w3c/element-timing#78).

However, looks like the "get an element" algorithm was not just moved over, but rather replaced with a very simple inline algorithm I think.

I am not sure if we should try to export a definition and make reference to it, or also just replace the algorithm and inline here.

CC @clelland for suggestions / oppinions.

@mmocny
Copy link
Contributor

mmocny commented Aug 19, 2024

Ah, looks like exposed for paint timing has mostly the same text as the original get-an-element, except it just returns true/false.

(I had expected that this was going to do more, such as limit to TAO only images, or something like that-- but it seems not.)

I will update using the same text as LCP now uses.

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