Skip to content

Conversation

@MartinNowak
Copy link
Contributor

  • self-closing void elements are an xhtrml thing
  • still preserve them as HTML5 (and most HTML4 parsers) are
    compatible and some people might prefer

- self-closing void elements are an xhtrml thing
- still preserve them as HTML5 (and most HTML4 parsers) are
  compatible and some people might prefer <br />
@MartinNowak
Copy link
Contributor Author

I'm a bit unsure about preserving the input. It might be better to always produce "correct" output regardless of the input.

@devebookingservices
Copy link
Contributor

Yes, I think the way to go is to have the parser be tolerant and eat anything it can understand, but then produce compliant markup of what it parsed.

devebookingservices added a commit that referenced this pull request Jan 26, 2016
@devebookingservices devebookingservices merged commit 98dcac6 into eBookingServices:master Jan 26, 2016
@MartinNowak
Copy link
Contributor Author

but then produce compliant markup of what it parsed.

Wait, then we should always output <br> no matter whether the input was <br> or <br />. Will make fixup.

@MartinNowak MartinNowak deleted the dont_self_close_void_tags branch January 26, 2016 10:34
@MartinNowak
Copy link
Contributor Author

See #9

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