Comments on: Page Weight and Semantics http://slightlyremarkable.com/blog/2005/12/05/page-weight-and-semantics/ Jonathan Fenocchi's personal weblog Sun, 05 Sep 2010 18:15:59 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Elliott http://slightlyremarkable.com/blog/2005/12/05/page-weight-and-semantics/comment-page-1/#comment-992 Elliott Mon, 06 Feb 2006 04:55:27 +0000 http://www.slightlyremarkable.com/?p=144#comment-992 I usually include snippits at the beginning of my style sheet in order to rob everything of it's built in attributes; padding, margins, list styles etc. That way I can build everything up from ground level using CSS. Definitely have to use a few more DIVs this way however. It obviously affects the weight of the template, but one CSS file to govern what... 3 sets of 66 pages. That must have saved some space :D I usually include snippits at the beginning of my style sheet in order to rob everything of it’s built in attributes; padding, margins, list styles etc.

That way I can build everything up from ground level using CSS. Definitely have to use a few more DIVs this way however. It obviously affects the weight of the template, but one CSS file to govern what… 3 sets of 66 pages. That must have saved some space :D

]]> By: Jona http://slightlyremarkable.com/blog/2005/12/05/page-weight-and-semantics/comment-page-1/#comment-797 Jona Sun, 18 Dec 2005 22:04:07 +0000 http://www.slightlyremarkable.com/?p=144#comment-797 Neuroxik, that's exactly my point. I see people complain on a constant basis that they don't want to add any additional HTML to their page, but still achieve the same appearance with CSS, while the job is much more easily done and more compatible when extra HTML (such as DIVs) is added. Neuroxik, that’s exactly my point. I see people complain on a constant basis that they don’t want to add any additional HTML to their page, but still achieve the same appearance with CSS, while the job is much more easily done and more compatible when extra HTML (such as DIVs) is added.

]]> By: Neuroxik http://slightlyremarkable.com/blog/2005/12/05/page-weight-and-semantics/comment-page-1/#comment-794 Neuroxik Sun, 18 Dec 2005 08:24:01 +0000 http://www.slightlyremarkable.com/?p=144#comment-794 Excuse me if I sound like a complete idiot if I do so by asking: Why would DIV's be considered extra and useless bulk if it only helps more than harms your file-size and markup habits? I mean, every place you can replace tables by divs, isn't that alot of bytes off? I mean, even your layout here uses divs, so what do you mean by non-semantic divs if they can only help in reducing size and having a more global control through css. Excuse me if I sound like a complete idiot if I do so by asking: Why would DIV’s be considered extra and useless bulk if it only helps more than harms your file-size and markup habits? I mean, every place you can replace tables by divs, isn’t that alot of bytes off? I mean, even your layout here uses divs, so what do you mean by non-semantic divs if they can only help in reducing size and having a more global control through css.

]]> By: Mike Cherim http://slightlyremarkable.com/blog/2005/12/05/page-weight-and-semantics/comment-page-1/#comment-773 Mike Cherim Wed, 07 Dec 2005 13:56:22 +0000 http://www.slightlyremarkable.com/?p=144#comment-773 I agree. I use divs and spans, and comments, as I see fit. I try to keep weight down in perhaps the most significant way: imagery. You're right, divs and spans having no meaning, no value. I think that's what bothers some purists. They feel everything should have meaning else it shouldn't be on the page. Bah. So what if a div has no meaning? It's still a way of organizing a page ( a division or a small span for style). As long as the div doesn't have display:none for a CSS attribute, as long as it's not used as a container that is supposed to be made with something else (think fieldset replacement as an example), and as long as it <em>contains proper, semantic mark-up</em>, I feel the harm factor is zero. I agree. I use divs and spans, and comments, as I see fit. I try to keep weight down in perhaps the most significant way: imagery. You’re right, divs and spans having no meaning, no value. I think that’s what bothers some purists. They feel everything should have meaning else it shouldn’t be on the page. Bah. So what if a div has no meaning? It’s still a way of organizing a page ( a division or a small span for style). As long as the div doesn’t have display:none for a CSS attribute, as long as it’s not used as a container that is supposed to be made with something else (think fieldset replacement as an example), and as long as it contains proper, semantic mark-up, I feel the harm factor is zero.

]]>