December 1st, 2007

I'll make this the last post on my site experiments.

One last change I did was to use the universal selector to eliminate margins and padding on all elements.

* { padding: 0; margin: 0 }

I also made an overall font adjustment in for the body element, so that 1em is equivalent to 10 pixels:

body {font-size: 62.5%; }

I find it easier to work with em units if I can put them into a general pixel reference.

Yes, I am aware of the issues with using the universal selector and eliminating all padding and margin settings. Yes, I am aware of Eric Meyer's own white space reset stylesheet, and his reasoning for setting specific elements.

In addition, I also use min-width and max-width to provide the outer layer around the centered content. With these, I can add as many outer bands of elements as I want and still have the page show up in smaller monitors with minimal scrolling. At the same time, the content doesn't look quite so thin on larger monitors.

Comments
1

I'm liking the new look. That whole whitespace reset thing can be quite a challenge when you are used to (being lazy like me and) working with the default whitespace. Looks like you've done it quite well, though.

2
carmen - 2:24 pm 12/2/2007

cool. now that your book is done, want to make your site load in Firefox?

heres the error:

XML Parsing Error: undefined entity
Location: http://burningbird.net/technology/lessons-from-the-book-final-thoughts/
Line Number 11, Column 24:Burningbird » Lessons from the Book: Final Thoughts
———————–^

and a screenshot:

its been broken for at least a year, to my recollection. and now that more people are using firefox3, its going to cut into your readerbase… if you care about that :)

http://whats-your.name/i/shelley.png

3
Shelley - 2:26 pm 12/2/2007

Firefox is my main weblogging tool. I've been beta testing with Firefox 3 before it was Firefox 3 and was Gran Paradisio. Here's a screenshot of my own.

Wordpress is not XHTML friendly, which is a problem I try to compensate for, and not always easily. However, you are the first person, ever, to tell me this isn't working in Firefox.

Which version of Firefox are you using, and in what environment? I don't have any quote in that title. Are you looking at the feed, rather than the actual page?

4
ralph - 3:42 pm 12/2/2007

The raquo entity that causes the error Carmen is seeing is the double-arrow thing that separates "Burningbird" from the rest of your title. It's a quotation mark in some European languages, hence the entity name.

I don't see any errors in Firefox 3.0b1 on my Mac.

The error Carmen is seeing looks like the copy of Firefox in use is trying to interpret the page as application/xml, which by default contains very few entities, rather than application/xhtml+xml, which contains the same entities as HTML 4.01. I have no idea why that would be happening, and I've never seen it when viewing (X)HTML pages, just when viewing raw XML (usually when testing something I'm doing with AJAX….)

5
Shelley - 3:53 pm 12/2/2007

Opera has problems with these named entities, but the most it will do is just print them rather than interpret them, not throw an XML error.

I can change the title to remove the named entity, but it still doesn't answer where this error is arising. I would assume Firefox operates the same regardless of environment.

6
Eric Meyer - 6:28 pm 12/2/2007

I almost hate to bring this up, but it's "Meyer". Thanks.

7
Shelley - 8:05 pm 12/2/2007

Sorry, I corrected your name.

8
carmen - 10:41 pm 12/3/2007

ralph: content-type is application/xhtml+xml according to the Page Info dialog.

im going to sneak into about:config and try to force everything to be parsed as HTML5, since its likely to be more lenient and designed for real world content, and will proably at least halfway hack proper XHTML into displaying, instead of outright failure :)

9
Shelley - 9:56 am 12/4/2007

carmen, you're not making any sense at all. None.

You came into my comments, you drop a note about how this isn't working with Firefox 3, only to come in later and say you're using a hacked together system. Did you stop to think it was your hack, not my page?

This is 'proper' XHTML, or Opera, Firefox (2 and 3), and Safari would all fail.

Next time? Download the pre-built version of Firefox and use it.

Thanks to all those who have contributed to the discussion. Comments are now closed, but you can contact the author of the post directly.