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

Self closing field should be ignored for tags that aren't self closing per spec #917

Open
EasonShi opened this issue Jul 15, 2017 · 5 comments

Comments

@EasonShi
Copy link

example

<a />content</a>
Parsed into
<a></a>content

@jhult
Copy link

jhult commented Jul 25, 2017

@EasonShi, what would you expect the output to be?

@jhy
Copy link
Owner

jhy commented Jul 25, 2017

Actually I looked at this the other day but forgot to add my notes. The spec and Chrome will ignore the self-closing flag. (So it would parse as <a>content</a>.) It looks like the spec has changed a bit since I implemented it, or that I missed the note, that an invalid self-closing flag should be rejected, and not just emitted as an error.

Need to check what impact that has as a behavior change.

@jhy jhy changed the title Compatibility Self closing field should be ignored for tags that aren't self closing per spec Jul 25, 2017
@antsher
Copy link

antsher commented Feb 6, 2019

Are there any news when this is going to be fixed?

@jhy
Copy link
Owner

jhy commented Dec 14, 2024

I am thinking of addressing this by renovating how we hold properties in Tags, and allow configuration of self-closing / void tags. And then moving the HTML default back into spec.

@jhy
Copy link
Owner

jhy commented Mar 12, 2025

Planning on changing this to align to the spec once #2285 Custom Tags is done

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

4 participants