Skip to content

Validator#32

Closed
beingzoe wants to merge 3 commits into
necolas:masterfrom
beingzoe:validator
Closed

Validator#32
beingzoe wants to merge 3 commits into
necolas:masterfrom
beingzoe:validator

Conversation

@beingzoe
Copy link
Copy Markdown

Hello.

These commits are trivial in nature. The idea was to make the demo.html validate (I was using it as part an "article" in my test doc for my new html5 markup - utilizing h5bp and by proxy normalize.css).

I realize demo.html can't actually validate even with these changes since the html5 spec is not complete and some of the elements you are demoing can't be tested for without warnings regardless.

However, the items I fixed that weren't validating are actually "illegal/obsolete" in html5.

Of the three edits, the one regarding closing tags on foreign elements surprised me. I thought we were free of the mandatory closing tag (I even began to wonder how many opening tags we would need to use anymore ;)

The other two edits are truly trivial and I said so in the commit. Just thought since I am using html5, and others might be turning to you and h5bp for the "right" way you might be interested.

Anyway, use if you want. I haven't made a pull request yet (still getting a handle on git) and this seemed like a nice safe place to start.

merry day,
zoe

… validation of demo.html)

From http://www.w3.org/TR/html5/syntax.html
Foreign elements must either have a start tag and an end tag, or a start tag that is marked as self-closing, in which case they must not have an end tag.
Looked like the project was geared towards html5.
Ignore if you are being html agnostic.
The summary attribute is obsolete. Consider describing the structure of the table in a caption element or in a figure element containing the table; or, simplify the structure of the table so that no description is needed.

Looked like the project was geared towards html5.
Ignore if you are being html agnostic.
@necolas necolas closed this in 54aa150 Aug 30, 2011
@necolas
Copy link
Copy Markdown
Owner

necolas commented Aug 30, 2011

I've sorted this stuff out and a few other things, like changing to valid value values. Thanks!

@beingzoe
Copy link
Copy Markdown
Author

No problem. I felt lame being the validator wonk but somebody had to be ;)

Oh, and if you didn't see I submitted an issue (without code) discussing an situation I discovered where FF 6 is styling h1's nested inside html5 section containers using their proposed any() selector. Kind of seems like a big deal to me, I list what I am doing to get around it temporarily, but thought it warranted discussion as to expected (normalized) behavior. I would have submitted a pull request for that but I haven't tested my normalization enough to know if it could be causing other problems.

Anyway, enjoy your day, and thanks for maintaining normalize.css in conjunction with h5bp!

@suarezph
Copy link
Copy Markdown

hello good day!, i have a read and use this normalize.css for my project. But suddenly my company didn't accept this css because it did not validate to w3c. i know its good and it is very helpful. :(

sigridfuhrenkamp-cyber pushed a commit to sigridfuhrenkamp-cyber/normalize.css that referenced this pull request Mar 9, 2026
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