Web Style Guide

[quasi-modo]

I'd say you're not supposed to design web pages that look the same on all browsers. Making a design that requires a page to look exactly the way you tried to make it look is making a flawed design.

what? If a page is designed with only ie in mind, you are saying it is ok if it gets masacred in mozilla? What??? That makes no sence at all. You should try to design so that your page performs in all browser well, this is not possible because for every mozilla firebird there is an ns4 (sort of like for every rose there is a thorn). So atleast make it so the content is always accessable. That is how I try to do things. Storm, about the id class thing, I use them both myself, if its one thing I use id, if Its multi I use class, and if one element in a class has a slight variation I use the style attribute right on that element, thats just my little way of doing things.

[Grok]

All the HTML that I currently write is for web pages.  Even so, I practice writing valid XHTML 1.1 for the day when I will need to consider more devices.  When that day comes, fuck all the NS4's, IE4's, and other noncompliant browsers.  If people have problems viewing my content when it's written tight and nice, they need to upgrade their viewing device.

[Adron]

what? If a page is designed with only ie in mind, you are saying it is ok if it gets masacred in mozilla? What???

Design and test in Lynx. I'm sure IE and Mozilla will be able to render whatever works in Lynx. And don't make extreme-precision things adding and removing pixels here and there. Describe what you want in a rough sort of way and allow the browser to make the best of it instead of tweaking and tweaking until you have a solution that only works on the platforms you have tested it on. Remember that your user might have his own style sheet that he applies to your page.

[quasi-modo]

Design and test in Lynx. I'm sure IE and Mozilla will be able to render whatever works in Lynx. And don't make extreme-precision things adding and removing pixels here and there. Describe what you want in a rough sort of way and allow the browser to make the best of it instead of tweaking and tweaking until you have a solution that only works on the platforms you have tested it on. Remember that your user might have his own style sheet that he applies to your page.

Heh, I actually do have a copy of lynx and I do preview my pages in it, I like css because it can break down for text based browsers into a plain text form real nicely. But I do have ie5, 5.5, 6, mozilla, opera, and netscape running here on this comp that I preview in too. I try to get those to look exactly the same aestetically, while older browsers I focus on the content being accessable. I do go for precision and I do use pixil perfect layouts a lot of the time (where if it does not line up perfectly it looks like crap, for example rounded courners), but that is where hacks come in, the box model in particular for ie5, 5.5.

[Adron]

Making something exact to the pixel makes no sense when suddenly one user has a 60 pixels/inch monitor and the next has a 150 pixels/inch monitor, since one will have three times "as big" (pixel-wise) fonts as the other.

[Grok]

Making something exact to the pixel makes no sense when suddenly one user has a 60 pixels/inch monitor and the next has a 150 pixels/inch monitor, since one will have three times "as big" (pixel-wise) fonts as the other.

It makes sense if you're writing with the intent to address a printed page.  That intent is specifically covered in XML-FO however and you should be using XML-FO and XSLT instead of XHTML/CSS.

[quasi-modo]

http://quasi-ke.servebeer.com/layout/index.aspx when I say pixil perfect I say everything lines up to the pixil, the borders are in css, yet the corners are images. It is also fluid and is not platform specific. That is going to be the layout for my clan's site. I am redoing everything on it just about so it is still far from finished. I am going to turn the news column into  a weblog, redo the forum, etc. Also, I am going to redo the banner when inspiration strikes me... the one now is just temporary.

[Adron]

Making something exact to the pixel makes no sense when suddenly one user has a 60 pixels/inch monitor and the next has a 150 pixels/inch monitor, since one will have three times "as big" (pixel-wise) fonts as the other.

It makes sense if you're writing with the intent to address a printed page.  That intent is specifically covered in XML-FO however and you should be using XML-FO and XSLT instead of XHTML/CSS.

It doesn't make sense on printed pages either, if you translate pixel-perfect to dot-perfect. Because sizing things by dots would mean that the document would print half-sized on a 1200 dpi printer if it was designed for a 600 dpi printer.... That's why sizing by pixels is bad.

[Grok]

Oh, I left that part out -- XML-FO (Formatting Objects) is precise to a point, which I think is 1/1200 of an inch.