that other guy's thoughts

Sun	Mon	Tue	Wed	Thu	Fri	Sat
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31

July 02, 2003

Ahhhh...Fignuts!

well apparently IE6 and Mozilla interpret even the basic CSS coding differently. But do not be alarmed, a plan is being formulated while you read this. My initial reaction is to just f-bomb the mozilla users (hi juby) and please the other 90% of the world with minimal effort. But that would be easy, and I'm not good at easy.

WARNING: tech speak ahead

okay, I just started the re-mockup here and I've already noticed a few problems. Mozilla apparently anchors the borders on the edge of the box and exands the thickness of the border toward the inside, wheras IE expands outward. This is probably a designed behavior for both browsers so I may be screwed no matter what.

The second problem is the background image rendering, IE seems to be stuck with a 20 pixel left padding for the top banner. There is neither padding nor margin of any sort assosicated with it. Mozillia has no such problems, but seems to have an unhealthy obsession for centering and an apparent disdain for resizing.

If I can't get this all standardized, I'm leaning towards setting up seperate templates for both IE and Mozillia and implanting a browser detection script in the inital page load, the re-directing as necessary. Anybody know how to do this and/or if it's even possible? Other suggestions or links to CSS references are welcomed, as I am relatively new to complex site design.

Posted by Kyle at 04:34 AM | Category: Website

Comments

I don't quite see what you mean about the borders, catch me sometime and show me.

As for the image rendering, have you tried setting padding-left for the banner to 0? What about for the body - that's always something that slips me up, is that the very body tag itself (i.e., the rendered part of the page) has a slight padding on it. It may also just be differences in rendering the image.

All in all, though, browser detection shouldn't be an issue. Scope out my mockup (http://www.juby.net/mockup.html) to see how I implemented a few things. I'm sure you've already found this, but just in case, check out the W3C's CSS reccomendation (http://www.w3.org/TR/REC-CSS1 and http://www.w3.org/TR/REC-CSS2 for CSS1 and 2, respectively). The reading is dry as hell, but anything you need to know about the raw coding will be there.

Posted by: juby at July 2, 2003 06:11 AM

Oh yeah, and the anti-mozilla sentiment? Keep in mind that if Microshaft ever pulls its head out of its ass and starts implementing the CSS1 spec (as opposed to the CSS1 core), your page will go to shit there, too. As well as the users of older browsers, which implement CSS even more crappily than Internet Exploiter.

In general, proper coding is a good idea. You never know when, for some reason, your small amount of web experience will be called into play.

Posted by: juby at July 2, 2003 06:15 AM

I don't really have an anti-mozilla sentement, I really have a "browsers don't interpret code the same" Honestly, I don't care who's right and who wrong, I just wish everybody went to the same thing. My F-bomb remark comes out of shear laziness on my part, I don't want to have to code any more than necessary, valid or not.

Posted by: Kyle at July 6, 2003 02:45 AM