本文主要是介绍css中div和spand,You can still use div，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！
48 Responses on the article “You can still use div”
> * For those who haven’t encountered this term before, flow content elements are the same as HTML 4’s block-level content elements.
No, it’s not. It’s similar to HTML4’s %flow. That is, both block-level and inline elements.
Yes! Most assuredly I use divs. As you described, I use a div now and then to call the reader’s attention to a couple of sections in an independently-styled block. A good example for me is, an inset box floated to the right of the main text, shaded and with a border, with perhaps a “Did you know?” section and a “For more information…” section.
Shouldn’t the Element be used to wrap the intro to a text?
Does this mean those html grid systems, with a gazillion div’s, will go away? Thx
I’m missing the “role” attribute. It is so useful!
When I look under the hood of some sites built in HTML5, I often do not see any elements in use at all, which is scary to me. The overuse of , and other new HTML5 elements, does not always make sense, semantically. While the overuse of the element can potentially make the markup messy and bloated (depending on where and why it is being used), it will always be the greatest tool when styling is needed on a block of content (exactly as this article states).
I should also mention that I literally just had “” tattooed on my left wrist, and “” on my right wrist just five days ago. I have strong feelings for it.
When I look under the hood of some sites built in HTML5, I often do not see any
I should also mention that I literally just had
Good article, though I wouldn’t focus as much on the stylistic needs for using divs.
When there is a need to style, it usually comes forth of a need to structure. I use a site (page) wrapper too, but I use it to differentiate the page content from possible overlays which lie outside the natural content of my page. That way the wrapper leaves enough room for structural flexibility, even when there are no overlays defined.
Nice! I’m working HTML5 and I’m using for align the element block. and for elements children
Still have questions. If sections are not to be used to create containers and/or for styling, it seems that that the use of html5 will see an expansion of file sizes as the ‘semantic’ elements are added for semantic purposes while we still carry around all the div statements for physical structure and styling of such. This seems especially hard for CMS’s that integrate multiple chunks of specialized html. Is
<div id=comment>
<article>
better than
<article id=comment> ?
i loved to have a wrapper tag named like and which could have been the real wrapper of the whole content under body. maybe next time :)
[…] article, read it by yourself at HTML5Doctor This entry was posted in Uncategorized. Bookmark the permalink. ← New site, […]
David: I think you slightly misunderstood Mike. You may style sections, but you may not add sections for the sole purpose of styling if the contained element do not represent a logical subdivision of your content.
But that’s for the ideal HTML5. However in on a practical case this is different if you want to author HTML5 today while there is still a significant amount of browser that do not understand it.
If you take for instance IE, you cannot style unknown tags and in this specific situation article, section and al are in this case. As Mike evoked it, you may use javascript to make IE understand them, but this only work if javascript is enabled. Therefore, relying on additional div for styling is required in this case. Indeed you would see an increase of tags, but this is transitional (and when you see how many IE6 are still in use, you can infer the transition will be long).
re: M/ Delahaye. Makes sense but will be an effort in reality I think. Code purpose change as they evolve and I think I will spend some time going back over code to be comfortable about appropriate use of html5. But then, code review never really hurts.
I expect that htmlshiv.js or modernizr.js will suffice for older browsers for now as I’m not sure I need to worry about javascript being turned off that much. Is this more likely than running ie6?
[…] You can still use div | HTML5 Doctor. This entry was posted in Uncategorized. Bookmark the […]
imo, using new tag are someway to other people working on it really know what it mean!
When you put ,.. ,,,no one know really what u means if they user other language like …etc
Using makes it more clear and make the front-end development easier!
I wish with html6, we never worry about special , tag will be anything we want! Looks at this markup:
quite beautiful, right?
[…] If you need a
Thank you for the great information. I am a web builder. I am always used this tag for templates development and alignment setting. In my point of view the tag is a very powerful tool for Web developers. I know most of them web developers are using this tag instead of tag for alignment setting and designing. This tag used to we can easily make CSS code. Many internet research writers are written an article and blog about web designing and CSS designing. You can easily buy research papers template development techniques of web templates and coding system.
[…] You can still use div | HTML5 Doctor (html5doctor.com) […]
I’ve started to feel that I’ve been overusing the section element so this article’s helped to confirm my fears. Should I be using divs more for “sections” of the page, such as containers for non-textual elements? (Banners, etc)
Of course, if you only want to style the first paragraph, you could use a CSS selector like h1 + p {} or article p:first-child {}.
In that case, “article p:first-child {}” wouldn’t work – ‘p’ isn’t the first child of ‘article’, the ‘h1’ is. It should be “article p:first-of-type {}”.
“:first-child” always trips me up.
[…] HTML5 Doctor (a community site I co-curate) including You can still use div […]
[…] HTML5 Doctor (a community site I co-curate) including You can still use div […]
@skottey:
I should also mention that I literally just had tattooed on my left wrist, and on my right wrist just five days ago. I have strong feelings for it.
So, you didn’t close the div?
You aren’t a div unto yourself?
;-)
pfft.
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.
Hi Friends,
I really dont like the using the divs, it really sucks.
Is it fine I to keep using table tag, become it is really easy to do.
Please give ur suggestions.
[…] используйте старые добрые
[…]
Blog post title
Blog post content
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! […]
I really enjoy this article, and the use of div’s
thank you.
@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
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.
[…] or as html5doctor concluded: You should use
Thanks so much – very helpful…
I disagree with wrapping the p with an intro div. Why not just put the class on the p itself. It makes no sense to use a div there. It’s less semantic, bloats up the markup, adds a nonsensical hierarchy, and provides no value. You are specifying that the p is special in a certain way, so the class goes on the p, you don’t use extra markup to specify that.
@Tim – If you take a closer look at my example you’ll see I have two paragraphs in the “intro”
If you take for instance IE, you cannot style unknown tags and in this specific situation article, section and al are in this case. As Mike evoked it, you may use javascript to make IE understand them, but this only work if javascript is enabled. Therefore, relying on additional div for styling is required in this case. Indeed you would see an increase of tags, but this is transitional (and when you see how many IE6 are still in use, you can infer the transition will be long).
Thanks a lot, your post made it much clearer to me.
Luckily, no need to rewrite already existing and working markup :-) Nice
You’ve got it completely wrong… it’s all the way down!
Ok so I’m completely way behind here. I have been hesitant on using ‘section’, ‘article’, etc. I would like to start using these more though I have been implementing ‘header’ and ‘footer’ for a sometime now. In the world of interwebs information regarding what is the most concrete thing to do can be fuzzy at times. I’d much rather prefer someone say, “no more divs” :) It makes it more concrete and less confusing. When someone looks at my code, I don’t want them going, “Ha they’re using html5 doctype and have no damn sections or articles…all I see is divs.” Good article. I will still use my divs
Join the discussion.
Name (required)
Mail (will not be published) (required)
Website
Some HTML is ok
You can use these tags:
You can also use , and remember to use < and > for brackets.
Enter comment
Notify me of followup comments via e-mail
这篇关于css中div和spand,You can still use div的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！
