Skip to content

rustdoc: replace DIV inside H1 with SPAN. #17529

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

Closed
wants to merge 1 commit into from

Conversation

nodakai
Copy link
Contributor

@nodakai nodakai commented Sep 25, 2014

W3C HTML5 spec states that H1 must enclose "phrasing content" which
doesn't include DIV. But SPAN is OK.
http://www.w3.org/TR/html5/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements

W3C HTML5 spec states that H1 must enclose "phrasing content" which
doesn't include DIV.  But SPAN is OK.
http://www.w3.org/TR/html5/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements
@Gankra
Copy link
Contributor

Gankra commented Sep 25, 2014

Have you confirmed that this doesn't break anything? Would you be able to host a rustdoc build to demonstrate?

@nodakai
Copy link
Contributor Author

nodakai commented Sep 25, 2014

@gankro Please take a look at http://nodakai.github.io/rust-6fd144c-doc/

This change improves W3C validator score:

@Gankra
Copy link
Contributor

Gankra commented Sep 25, 2014

@nodakai Thanks!

bors added a commit that referenced this pull request Sep 28, 2014
W3C HTML5 spec states that H1 must enclose "phrasing content" which
doesn't include DIV.  But SPAN is OK.
http://www.w3.org/TR/html5/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements
@bors bors closed this Sep 28, 2014
@nodakai nodakai deleted the rustdoc-div-in-h1 branch September 28, 2014 15:56
lnicola pushed a commit to lnicola/rust that referenced this pull request Jul 11, 2024
fix: Fix lifetime parameters moving parameter defaults

Fixes rust-lang/rust-analyzer#17075, rust-lang/rust-analyzer#17515

We were incorrectly filling the default params due to our odd order of lifetime parameters vs type/const params. So this needs some special handling so that we don't shift the defaults around.
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.

4 participants