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

All void elements should be self-closing #39

Merged
merged 2 commits into from
Nov 7, 2014
Merged

All void elements should be self-closing #39

merged 2 commits into from
Nov 7, 2014

Conversation

OscarBarrett
Copy link
Contributor

According to the HTML5 specification hr elements should not have an end tag.
http://www.w3.org/TR/html5/grouping-content.html#the-hr-element

@OscarBarrett
Copy link
Contributor Author

Noticed #26 after submitting this, which is pretty much the same issue. So I've updated the PR to make all void elements self-closing.

The list of void elements was taken from here:
http://www.w3.org/html/wg/drafts/html/master/syntax.html#void-elements

expect(arbre {
br
}.to_s).to eq("<br/>\n")
(Arbre::HTML::Tag::SELF_CLOSING_ELEMENTS).each do |tag|
Copy link
Member

Choose a reason for hiding this comment

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

remove the ()

@timoschilling
Copy link
Member

You don't need to create a new PR again. You can simply force push to your feature/void_elements branch to update this PR

@OscarBarrett
Copy link
Contributor Author

Updated. I made a new PR for the commit changes so that the original comments from the previous PR were preserved. I wasn't aware that GitHub preserves outdated diffs though.

@timoschilling
Copy link
Member

Thats not necessary, github shows the comments as outdated and link them to the old commit (see above). So there is now reason to create a new PR

timoschilling added a commit that referenced this pull request Nov 7, 2014
All void elements should be self-closing
@timoschilling timoschilling merged commit 22ee808 into activeadmin:master Nov 7, 2014
@OscarBarrett
Copy link
Contributor Author

Yeah, I wasn't aware of that. Thanks.

@timoschilling
Copy link
Member

I have copied to PR description and your first comment from #35 to here for a better documentation

@ybart
Copy link

ybart commented Nov 7, 2014

Thanks !

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.

3 participants