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

Add integration with setHTMLUnsafe and parseHTMLUnsafe #406

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

lukewarlow
Copy link
Member

Fixes #403

Couldn't seem to get the functions to link to the right place in the HTML spec. But none of the methods in the IDL are linking as expected so perhaps there's a deeper issue?

@lukewarlow lukewarlow marked this pull request as ready for review January 15, 2024 19:53
@lukewarlow lukewarlow requested a review from koto January 15, 2024 19:53
@lukewarlow
Copy link
Member Author

cc @koto @mbrodesser-Igalia

@koto koto merged commit 6676495 into w3c:main Jan 17, 2024
2 checks passed
github-actions bot added a commit that referenced this pull request Jan 17, 2024
SHA: 6676495
Reason: push, by koto

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@mbrodesser-Igalia
Copy link
Collaborator

Couldn't find WPTs for this, so they'll presumably have to be added.

@lukewarlow
Copy link
Member Author

Yeah Joey will add them when he fixes in chrome or if I get round to it first I'll add them in a WebKit patch. Should be a trivial test

@mbrodesser-Igalia
Copy link
Collaborator

Btw, in other specs, sometimes spec issues like this one link to the engines' implementation bugs and tests. Filed #415 for a general template.

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.

Missing integration with new unsafe HTML parsing methods
3 participants