We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
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.
mmocny
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: