Skip to content

Edit the list of possible initiatorType values. #418

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

Merged
merged 3 commits into from
Aug 5, 2025

Conversation

guohuideng2024
Copy link
Member

@guohuideng2024 guohuideng2024 commented Jun 26, 2025

Update the list.

Bug: #364


Preview | Diff

The link to "Early hints" is broken. Will need to export that
in html spec to make this PR valid.

Bug: w3c#364
@guohuideng2024
Copy link
Member Author

guohuideng2024 commented Jun 26, 2025

I made this edit mostly based on https://developer.mozilla.org/en-US/docs/Web/API/PerformanceResourceTiming/initiatorType, Chromium and WPT test.

Decision of the values modified/added here is based on
#364 (comment)

Below is the list of things that are not obvious. And I need some guidance on some of them.

  1. For the "body" value, it's used for the "background" attribute in "body" element, which is obsolete now. That's why there is no reference link to the current html standard.

I am not sure if the current text is appropriate, and I am not sure if I should include the "body" value in this list because this is obsolete now.

  1. Looks like the "ping" replaced "a" and it's for the "ping" attribute only.

  2. The link to "Early hints" is broken. I cannot find an exported reference to "early hint" on
    https://respec.org/xref/
    and I see the "fetch" standard is not refereeing it either. (see the third note on
    https://fetch.spec.whatwg.org/#fetching )

So I plan to submit a PR that adds a class="export" to the "Early hints" dfn in html spec. Is it a right move?

Thanks.

@guohuideng2024 guohuideng2024 requested a review from noamr June 26, 2025 22:15
@guohuideng2024
Copy link
Member Author

@noamr : I also filed a PR to fetch:
whatwg/fetch#1837

I would add you as a reviewer there but I don't have permission to add reviewers in the whatwg repo.

@guohuideng2024
Copy link
Member Author

guohuideng2024 commented Jul 2, 2025

@noamr : You mentioned font is used by IFT, I think I should add font here?

From https://www.w3.org/TR/IFT/, I see the following text:

"This document was produced by the Web Fonts Working Group as a Working Draft using the Recommendation track. This document is intended to become a W3C Recommendation."

So it looks like it's not yet adopted and implemented. (No wonder I cannot find it in Chromium and WPT).
Should I simply say something like: font value --> downloaded using IFT technology?

One more consideration: if we report the "initiator type" from IFT, wouldn't something like IFT be better than font because it's more specific? And imagine if in the future there is a different technology font_delivered_by_apple used with font, then we won't be able to distinguish between font_delivered_by_apple and IFT

Thanks.

@noamr
Copy link
Contributor

noamr commented Jul 2, 2025

@noamr : You mentioned font is used by IFT, I think I should add font here?

From https://www.w3.org/TR/IFT/, I see the following text:

"This document was produced by the Web Fonts Working Group as a Working Draft using the Recommendation track. This document is intended to become a W3C Recommendation."

So it looks like it's not yet adopted and implemented. (No wonder I cannot find it in Chromium and WPT). Should I simply say something like: font value --> downloaded using IFT technology?

One more consideration: if we report the "initiator type" from IFT, wouldn't something like IFT be better than font because it's more specific? And imagine if in the future there is a different technology font_delivered_by_apple used with font, then we won't be able to distinguish between font_delivered_by_apple and IFT

Not exactly. The font is the "initiator" of the request. You access a font, and that font "initiates" an IFT request.

@guohuideng2024
Copy link
Member Author

Sorry for the late update. Now this PR is ready for review.

I added some text to clarify between "font" and "css".

For the "Early-hint" reference, I actually filed PR to export it from html spec.
whatwg/html#11508
But for now I added it as localBiblio.

And I found out that I cannot use - in localBiblio name. I had to use _ instead.

index.html Outdated
</p>

<p>
Another example is, the request for a font resource specified
Copy link
Contributor

Choose a reason for hiding this comment

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

"Note:" instead of "Another example is,"

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

Copy link
Contributor

@noamr noamr left a comment

Choose a reason for hiding this comment

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

Looks good! see comment

1. "Another example is" ==> "Note:"
2. Update the reference of "early hints" with the rfc at IETF.
@guohuideng2024
Copy link
Member Author

guohuideng2024 commented Jul 31, 2025

In addition, per domenic@ 's suggestion at whatwg/html#11508,
I replaced the reference link to early hints with https://httpwg.org/specs/rfc8297.html
This change was made after the approval so I will wait until next Tuesday before I merge this PR.

Thanks.

@guohuideng2024 guohuideng2024 merged commit a504626 into w3c:gh-pages Aug 5, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants