Move TrustedParserOptions to TrustedHTMLParserOptions

[tunetheweb]

Summary

A follow on to #30328 with the following changes:

• TrustedParserOptions was renamed to TrustedHTMLParserOptions as part of standardisation review (note this is not complete yet) - w3c/trusted-types@b97634f. FYI @Elchi3 as think you might have manually added this t the BCD collector?

Test results and supporting details

https://wpt.fyi/results/domparsing/tentative?label=experimental&label=master&aligned

https://chromestatus.com/feature/5054329641893888

Related issues

A follow on to #30328

Web Features (referencing these keys, including TrustedParserOptions) - web-platform-dx/web-features#4318

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[Elchi3]

This seems all reasonable to me. The only thing is that I have no Chrome 155 beta yet and so I can't tell if it is really shipping.

[tunetheweb]

Yeah it was original in 154 (and even made the 154 beta!) but this TrustedHTMLParserOptions change made us decide to not rush it in for 154 with this last minute change and instead include in 155.

If you prefer I can leave it as behind a flag for now and just do the TrustedParserOptions -> TrustedHTMLParserOptions change in this PR? Or can leave this open for a week until the 155 beta is out.

[Elchi3]

Yeah, if you want this PR to land then just the renaming would be great. Ideally the collector run for 155 beta should pick up this as shipping next week then. But you can also leave this PR open as is and we get to it next week when we have the 155 beta. As you prefer :)

[tunetheweb]

No real urgency for this to land as the TrustedHTMLParserOptions is more a technical concept rather than the API used directly by developer (though it might affect typescript).

But I thought it would mess up your collector if that didn't land. So let's land it and let the collector manage the 155 update.

Have reverted the other changes now. PTAL.

[github-actions]

The lint check found auto-fixable issues. Apply suggested changes (attributed to bcd-linter), or to fix all at once, run npm run lint:fix locally.

See also: Automated lint suggestions on pull requests

[Elchi3]

Thank you, @tunetheweb 👍

[Elchi3]

Yeah it was original in 154 (and even made the 154 beta!) but this TrustedHTMLParserOptions change made us decide to not rush it in for 154 with this last minute change and instead include in 155.

If you prefer I can leave it as behind a flag for now and just do the TrustedParserOptions -> TrustedHTMLParserOptions change in this PR? Or can leave this open for a week until the 155 beta is out.

fwiw, I am not seeing this enabled in Chrome 155 beta that is available now.

[tunetheweb]

Confirmed! Thanks for spotting that. Chasing with engineering now...

[tunetheweb]

FYI, @Elchi3 this has been pushed back to 157 now due to some other changes as part of standardisation.