I have a div element with an assigned background image. Within the div block, at the top I have an image which appropriately give the appearance of rounded corners... followed by the content (text) followed by an image which appropriately gives the appearance of rounded cornders (for the bottome of the div block).
The problem is, the backgroundimage for the div elment appears just above and just below (like 3px of it) the images which should "round" the corners.
Adding extra HTML markup just to fix a display problem... may as well be using tables."
Well, up until recently, the use of tables was acceptable. And for the most part, it still is.
EDIT: Not saying we shouldn't embrace web standards or upgrade, but fretting over the use of DIVs, and their likeness to how tables are used for layouts is silly. However, since there's an alternative, go for it.
[This message has been edited by MedHead (edited 02-24-2004).]
quote:Well, up until recently, the use of tables was acceptable. And for the most part, it still is.
I have no idea where you're getting that idea from. Who exactly deems something as acceptable? And in what context? I thought we were talking about web standards here.
quote:Not saying we shouldn't embrace web standards or upgrade, but fretting over the use of DIVs, and their likeness to how tables are used for layouts is silly.
No, it's not silly at all.
Web standards aren't just about not using <tables>s for layouts, if you think that's what it is then I fear you're missing the point.
CSS is about separating display from content. An extra <div> thrown into a page to fix a display problem is defiantly in opposition to this ideal. This is what web standards are all about. CSS is just a technology, like <table>s, how you use this technology is the measure by which I would consider a website to be standards compliant.
[This message has been edited by Cameron (edited 02-25-2004).]
quote:I have no idea where you're getting that idea from. Who exactly deems something as acceptable? And in what context? I thought we were talking about web standards here.
I would consider W3C as a good source for choosing standards. Tables are still allowed under XHTML Transitional, I believe. How they're used is really the business of the owner of the website, and nobody else.
While XHTML was recommended back in 2000, it hasn't really gained a real foothold even now. Serious designers use that format to follow the recommendations (and it appears, only for that reason, which smacks of elitism), but it hasn't hit the amatuer market yet (for instance, up until Dreamweaver MX, DIV layouts weren't supported by Dreamweaver). For the most part, tables are still here to stay. People can scream about standards all they want, but if nobody uses them, they're not really standard, are they?
quote:No, it's not silly at all.
Web standards aren't just about not using <tables>s for layouts, if you think that's what it is then I fear you're missing the point.
CSS is about separating display from content. An extra <div> thrown into a page to fix a display problem is defiantly in opposition to this ideal.
Yes, just like tables were. Just like the Internet is now today. The Internet wasn't originally intended for what it is today - does that mean it's bad? Good grief, no need to be anal. DIVs are the structure of the page. He needed a fix, I gave him one. I didn't recall the display: block option - I already said that was a better idea. But you're jumping on me because I (gasp) offered to use another DIV?!
quote:This is what web standards are all about. CSS is just a technology, like <table>s, how you use this technology is the measure by which I would consider a website to be standards compliant.
An extra DIV will not destroy a page, nor will it make the load time balloon, nor will it look any different in any browser. You're blowing things way out of proportion. "Oh no! He used an extra DIV! I'm never going back to that site ever again! He's not following web standards!111"
Dang dude, calm down. This is a discussion forum. People, um, discuss things here.
I'm not jumping on you about anything, merely disagreeing with your point of view. If you don't like people disagreeing with what you say, don't say anything. =)
Anyways, I think the main disagreement here is what web standards are all about. Obviously you see them as a technology spec to be used any which way you want, as long as it works. I however, disagree (no surprises there). I see standards as a way to promote better practices and to better the future of the web. So do the W3C and many others who promote them. Yet now I?ve been called an elitist, and for what?
How does wanting the web to be more usable, accessible and interoperable make me elite?
Yes, <table>s are allowed in XHML, but I disagree with you as to how they should be used. The W3C recommendations may make it possible for you to make a table based layout, but does that mean they promote this practice?
The recommendations loosely cover what the provided elements are designed to be used for. Tables are just that. A table is not a template. It is a means to mark-up tabular data; as such it has its uses but should not be used to encapsulate the layout and visual presentation of an entire document.
Furthermore, just because it's not in widespread use doesn't mean it's not useful. The fact of that matter is that most websites are in HTML, the majority of which don't follow the recommendations set out by the W3C. I'd suspect this is because they don't know any better, having not actually read up on the technology they are using. This is just as bad as any excuse for not using them correctly.
quote:An extra DIV will not destroy a page, nor will it make the load time balloon, nor will it look any different in any browser. You're blowing things way out of proportion. "Oh no! He used an extra DIV! I'm never going back to that site ever again! He's not following web standards!111"
Dude, this discussion stopped being about just one <div> element when you started saying that using tables were an acceptable way to display websites. At which point I thought we moved onto a discussion about web standards and best practices.
[This message has been edited by Cameron (edited 02-26-2004).]