Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Proper (meaning valid and semantic) Markup and CSS, Please.
This discussion has been closed.
Comments
oh spookyET, you so crazy
Before people think I'm mad. That is a reference to waht ithcy said.
*lech claws his eyes out post-haste.
And at the bottom of the page, it says "101 to 150 of 352" or whatever, so the numbers would go from 101 to 150.
Mark: while I like his discussion list markup, I do not think his use of blockquote and cite in the comment page are appropriate.
Well there's a semantic logic to using those tags. Also, I feel the numbering of the ordered list is simply the default rendering in a browser and its underling semantic meaning is what's important.
I'm beginning to really doubt the philosophy that, whenever you encounter a need for a tag that doesn't exist, you should shoehorn it into an existing tag with a vaguely similar meaning. At best, this does nothing but dilute the meaning of the tags we have.
In this case, the only information we can derive from your use of the blockquote tag is that the post was written by a person. Of course, so was every other piece of text on the internet, so the blockquote becomes just a fancy way to avoid divs, just like divs used to be a fancy way of avoiding tables.
We, as markup authors, need to be able to suck it up and admit that the HTML spec is not all-encompassing, that the tag we need may be outside the scope of the spec, and that it's perfectly alright to use a div when nothing else works.
And while the default rendering of a tag may not be as important as the semantic meaning of the tag (and I agree that it is not), that doesn't mean that default renderings are entirely unimportant; they may be all the user gets.
I just liked what Tantek was saying and thought this was a good case to try it out and see if it worked.