Comments on: You can still use div http://html5doctor.com/you-can-still-use-div/ helping you implement HTML5 today Tue, 22 May 2012 11:38:25 +0000 hourly 1 http://wordpress.org/?v= By: Is ProfitGuruOnTheWeb A Scam or Legit | Scam Or Legitimate? http://html5doctor.com/you-can-still-use-div/#comment-25880 Is ProfitGuruOnTheWeb A Scam or Legit | Scam Or Legitimate? Sun, 20 May 2012 20:08:18 +0000 http://html5doctor.com/?p=1853#comment-25880 [...] You can still use div | HTML5 Doctor [...] [...] You can still use div | HTML5 Doctor [...]

]]> By: smcdee http://html5doctor.com/you-can-still-use-div/#comment-25350 smcdee Thu, 26 Apr 2012 21:32:48 +0000 http://html5doctor.com/?p=1853#comment-25350 Thanks so much - very helpful... Thanks so much – very helpful…

]]> By: Why we should not get too semantic (or “CSS performance & a pleading for <div>”) | peter mühlbacher – blog http://html5doctor.com/you-can-still-use-div/#comment-25349 Why we should not get too semantic (or “CSS performance & a pleading for <div>”) | peter mühlbacher – blog Thu, 26 Apr 2012 19:13:52 +0000 http://html5doctor.com/?p=1853#comment-25349 [...] or as html5doctor concluded: You should use <div> when there is no other more semantically appropriate element that suits your purpose. Its most common use will likely be for stylistic purposes — i.e., wrapping some semantically marked-up content in a CSS-styled container. (full article: http://html5doctor.com/you-can-still-use-div/) [...] [...] or as html5doctor concluded: You should use <div> when there is no other more semantically appropriate element that suits your purpose. Its most common use will likely be for stylistic purposes — i.e., wrapping some semantically marked-up content in a CSS-styled container. (full article: http://html5doctor.com/you-can-still-use-div/) [...]

]]> By: Narayguy http://html5doctor.com/you-can-still-use-div/#comment-24677 Narayguy Sun, 26 Feb 2012 19:40:17 +0000 http://html5doctor.com/?p=1853#comment-24677 Pretty darn helpful. I'm new to HTML 5 but it's nice how there are overlaps. Personally, I run a <a href="http://www.honestcollege.com/" rel="nofollow">college advice</a> site and am mainly focused on writing, but knowing a few HTML hacks never hurts. Pretty darn helpful. I’m new to HTML 5 but it’s nice how there are overlaps. Personally, I run a college advice site and am mainly focused on writing, but knowing a few HTML hacks never hurts.

]]> By: StnCham http://html5doctor.com/you-can-still-use-div/#comment-20568 StnCham Tue, 13 Dec 2011 22:06:03 +0000 http://html5doctor.com/?p=1853#comment-20568 @Dan <blockquote cite="skottey"> So, you didn’t close the div? You aren’t a div unto yourself?</blockquote> Ha! @skottey <blockquote cite="skottey"> I should also mention that I literally just had <code> < div></code> tattooed on my left wrist, and <code> < div></code> on my right wrist just five days ago. I have strong feelings for it.</blockquote> You know, since you didn't close, you'll not validate. :P @Dan

So, you didn’t close the div?
You aren’t a div unto yourself?

Ha!

@skottey

I should also mention that I literally just had < div> tattooed on my left wrist, and < div> on my right wrist just five days ago. I have strong feelings for it.

You know, since you didn’t close, you’ll not validate. :P

]]> By: HTML5 And The Document Outlining Algorithm | Free Android Updates http://html5doctor.com/you-can-still-use-div/#comment-17390 HTML5 And The Document Outlining Algorithm | Free Android Updates Sun, 28 Aug 2011 19:16:51 +0000 http://html5doctor.com/?p=1853#comment-17390 [...] Remember, you can still use div! [...] [...] Remember, you can still use div! [...]

]]> By: HTML5 And The Document Outlining Algorithm | www.aranda.se http://html5doctor.com/you-can-still-use-div/#comment-17336 HTML5 And The Document Outlining Algorithm | www.aranda.se Thu, 25 Aug 2011 14:07:29 +0000 http://html5doctor.com/?p=1853#comment-17336 [...] Remember, you can still use div! [...] [...] Remember, you can still use div! [...]

]]> By: HTML5 And The Document Outlining Algorithm | Just Info http://html5doctor.com/you-can-still-use-div/#comment-17326 HTML5 And The Document Outlining Algorithm | Just Info Thu, 25 Aug 2011 01:00:35 +0000 http://html5doctor.com/?p=1853#comment-17326 [...] Remember, you can still use div! [...] [...] Remember, you can still use div! [...]

]]> By: Stan http://html5doctor.com/you-can-still-use-div/#comment-17250 Stan Sat, 20 Aug 2011 19:26:14 +0000 http://html5doctor.com/?p=1853#comment-17250 I really enjoy this article, and the use of div's thank you. I really enjoy this article, and the use of div’s

thank you.

]]> By: HTML5 And The Document Outlining Algorithm | James Cacchione http://html5doctor.com/you-can-still-use-div/#comment-17216 HTML5 And The Document Outlining Algorithm | James Cacchione Thu, 18 Aug 2011 08:29:38 +0000 http://html5doctor.com/?p=1853#comment-17216 [...] <body> <article> <h1>Blog post title</h1> <p>Blog post content</p> </article> </body> The document is untitled. Somewhat reluctantly, Johansson settles on marking up the website’s title in h1 and using another h1 to mark up the article’s title. This is a sensible solution and is backed up by the results of the WebAIM screenreader user survey, in which the majority of respondents stated a preference for two top-level headings in exactly this format. This same approach is also widely used on static pages that are built with HTML5 structural elements, and it could be very useful indeed for screen reader users. Imagine that you are using a screen reader to find a decent recipe for chicken pie, and you have a handful of recipe websites open for comparison. Being able to quickly find out which website you are on using the shortcut key for headings would be much more useful than seeing only “chicken pie” on each one. Not too far behind two top-level headings in the screen reader user survey was one top-level heading for the document. This is probably my preferred option in most cases; but as we have already seen, it creates an untitled body, which is undesirable. In my opinion, there is an easy way around this problem: don’t use article as a wrapper for single-blog posts, news items or static page main content. Remember that article is sectioning content: it creates a sub-section of the document. But in these cases, the document is the content, and the content is the document. Setting aside the name of the element, why would we want to create a sub-section of a document before it has even begun? Remember, you can still use div! [...] [...] <body> <article> <h1>Blog post title</h1> <p>Blog post content</p> </article> </body> The document is untitled. Somewhat reluctantly, Johansson settles on marking up the website’s title in h1 and using another h1 to mark up the article’s title. This is a sensible solution and is backed up by the results of the WebAIM screenreader user survey, in which the majority of respondents stated a preference for two top-level headings in exactly this format. This same approach is also widely used on static pages that are built with HTML5 structural elements, and it could be very useful indeed for screen reader users. Imagine that you are using a screen reader to find a decent recipe for chicken pie, and you have a handful of recipe websites open for comparison. Being able to quickly find out which website you are on using the shortcut key for headings would be much more useful than seeing only “chicken pie” on each one. Not too far behind two top-level headings in the screen reader user survey was one top-level heading for the document. This is probably my preferred option in most cases; but as we have already seen, it creates an untitled body, which is undesirable. In my opinion, there is an easy way around this problem: don’t use article as a wrapper for single-blog posts, news items or static page main content. Remember that article is sectioning content: it creates a sub-section of the document. But in these cases, the document is the content, and the content is the document. Setting aside the name of the element, why would we want to create a sub-section of a document before it has even begun? Remember, you can still use div! [...]

]]>