3 ms·

Can anyone explain how this differs at all from resets? The only difference I see on the page is: > Preserves useful defaults and I don't know what a "user de

Can anyone explain how this differs at all from resets? The only difference I see on the page is: > Preserves useful defaults and I don't know what a "user default" is.

there 15y ago
when a user has a different default font and/or size selected in their browser?
- tealtan 15y ago
  Not user defaults, useful defaults. Some css resets strip out bullet styles for lists, or focus styles on selected text boxes. I assume this keeps things like that intact instead of nuking everything.
  - MatthewPhillips 15y ago
    Yeah, sorry, obviously I can't read. I would like to downvote myself right now.
lpolovets 15y ago
> and I don't know what a "user default" is. https://github.com/necolas/normalize.css/blob/master/normalize.css https://github.com/necolas/normalize.css/blob/master/normali... There's nothing earth shattering, but some things have non-zero margins, sub/sup have offsets, etc. CSS resets basically strip all default formatting, while this strips most of it.
emitstop 15y ago
This appears to normalize everything (make the default css consistent across all browsers) instead of removing the defaults altogether.
baddox 15y ago
It looks like it's just a baseline css file. Many resets and CSS frameworks come with those anyway, e.g. Blueprints typography.css: http://www.blueprintcss.org/tests/parts/elements.html http://www.blueprintcss.org/tests/parts/elements.html
ashearer 15y ago
Traditional resets require the CSS author to build styles for every element back up from nothing, or to remove the corresponding rules from the reset. In practice, you get into the situation where the designer doesn't encounter all those tags on a limited mockup page. Then when it comes time to build out the site, and the developer or author tries to format a list, or emphasize text with a <strong> element, neither has any effect at all. When it comes to visual style, any element not explicitly allowed by the CSS designer is denied. <strong> elements should generally show some kind of emphasis, probably boldface, but a full CSS reset sets them back to plain text. If all you've gained from the full reset is the opportunity to forget to set them back to boldface, what was the point? This project looks like an attempt to retain the most useful properties of a CSS reset (like consistent default element margins) while forestalling the process of redefining each element piecemeal to look pretty much like what the browser would have shown in the first place.
StavrosK 15y ago
"Useful", not "user".

Can anyone explain how this differs at all from resets? The only difference I see on the page is: > Preserves useful defaults and I don't know what a "user default" is.

there 15y ago

when a user has a different default font and/or size selected in their browser?

tealtan 15y ago
Not user defaults, useful defaults. Some css resets strip out bullet styles for lists, or focus styles on selected text boxes. I assume this keeps things like that intact instead of nuking everything.
- MatthewPhillips 15y ago
  Yeah, sorry, obviously I can't read. I would like to downvote myself right now.

lpolovets 15y ago

> and I don't know what a "user default" is. https://github.com/necolas/normalize.css/blob/master/normalize.css https://github.com/necolas/normalize.css/blob/master/normali... There's nothing earth shattering, but some things have non-zero margins, sub/sup have offsets, etc. CSS resets basically strip all default formatting, while this strips most of it.

emitstop 15y ago

This appears to normalize everything (make the default css consistent across all browsers) instead of removing the defaults altogether.

baddox 15y ago

It looks like it's just a baseline css file. Many resets and CSS frameworks come with those anyway, e.g. Blueprints typography.css: http://www.blueprintcss.org/tests/parts/elements.html http://www.blueprintcss.org/tests/parts/elements.html

ashearer 15y ago

Traditional resets require the CSS author to build styles for every element back up from nothing, or to remove the corresponding rules from the reset. In practice, you get into the situation where the designer doesn't encounter all those tags on a limited mockup page. Then when it comes time to build out the site, and the developer or author tries to format a list, or emphasize text with a <strong> element, neither has any effect at all. When it comes to visual style, any element not explicitly allowed by the CSS designer is denied. <strong> elements should generally show some kind of emphasis, probably boldface, but a full CSS reset sets them back to plain text. If all you've gained from the full reset is the opportunity to forget to set them back to boldface, what was the point? This project looks like an attempt to retain the most useful properties of a CSS reset (like consistent default element margins) while forestalling the process of redefining each element piecemeal to look pretty much like what the browser would have shown in the first place.

StavrosK 15y ago

"Useful", not "user".