Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/mislz28/public_html/wp-content/themes/css-faq-v2/timeweather/timeweather.php on line 19

From Eric Meyer’s page here is his new way of resetting his previous work:
_________________________________________________________
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
padding: 0;
border: 0;
outline: 0;
font-size: 100%;
vertical-align: baseline;
background: transparent;
}
body {
line-height: 1;
}
ol, ul {
list-style: none;
}
blockquote, q {
quotes: none;
}/* remember to define focus styles! */
:focus {
outline: 0;
}

/* remember to highlight inserts somehow! */
ins {
text-decoration: none;
}
del {
text-decoration: line-through;
}

/* tables still need ‘cellspacing=”0″‘ in the markup */
table {
border-collapse: collapse;
border-spacing: 0;
} ___________________________________________________________
Meyer’s explanations of the above codes and rules are as follows:

“Minute modifications involve a paring down of quotation around blockquotes and qs. Meanwhile the bigger modification includes the removal of the inherent values in the first rule—the one that wiped out boldfacing, font variants or italicizing in browsers except Internet Explorer.
[The inherit] effects, as seen in my development environment, will still serve the purpose of reminding me to build up the styles I actually want, and not use the browsers’ defaults as a crutch. There is the possibility of my forgetting that (for example) IE/Win italicizes em when I don’t want it to, but that’s something I’ll catch during the browser testing phase.
But over time, I’ve come to realize that this is more than just a throwaway development tool. It really is the beginning of a baseline style sheet. (Or can be.) Things like boldfacing and italics are some of the most obvious textual effects readers will see, and to have reset styles that treat them inconsistently across browsers doesn’t make sense.
Of course, browsers might treat elements differently when it comes to boldness and decoration and such. But unfortunately, without inherit as a viable solution (due to the lack of support in Explorer), we’re stuck accepting browser defaults. This is one area where defaults are pretty well consistent across the board, so it’s a small risk to be taking. And this certainly doesn’t preclude anyone from adding to these styles to create their own reset that explicitly handles elements like em and strong.
Which leads me to why I explicitly set ins and del. In some browsers, inserted text is underlined. This leads to confusion, because most people expect underlined text to be a link. I decided to explicitly switch that off and leave a note about it, much as I did with :focus styles.
And why am I not zeroing out deprecated elements, like center? Because they shouldn’t even be in the markup. The way to handle deprecated elements is with something like Marco Battilana’s Big Red Angry Text, not silently neutering them.”

The above words from the designer himself are going to clear up some questions about the reset. This is sure to convince others that there is more to CSS than mere styling.
To see more details, visit http://meyerweb.com/eric/thoughts/2008/01/15/resetting-again/.

Tags:

This entry was posted on 24 February 2008 at 7:40 PM and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One comment

1. 
Mod

Eric is really nice man, this resetting of style sheets is nice.

21 March 2008 at 11:59 AM

Leave a reply

Name (*)
Mail (will not be published) (*)
URI
Comment