Help Fix My Site's Css/layout Issues - Thanks for your time

The first issue has been resolved. Please goto Post #7 to see the current discussion.

This is in reference to: http://facesofwar.org/cms/

When you load the page up in Firefox it works fine. But when you use I.E. it creates a nasty line break after each of the spans containing a dividing line.

The relevant html is:


And the relevant css (for 1280 resolutions) is:


Thanks for your help ahead of time.

 

 

 

Comment/Reply (w/o sign-up)

I recently fixed unwanted line break with H1 tag by using this as part of stylesheet.



give it a try.

Comment/Reply (w/o sign-up)

Thanks for the suggestion, but it's a no go.

Comment/Reply (w/o sign-up)

If SPAN didn't work, then you should go ahead with DIV instead.

Rather than using class to define the structure of your web page, use ID



and of course your stylesheet should reflect accordingly.

If I was designing that navigation portion I would do something like this



And define stylesheet as

What you are trying to do is use the SPAN to draw the top borderline and another SPAN to draw the bottom line when stylesheet can define the whole process, including the hover instead of "mouseOver" effect.

 

 

 

Comment/Reply (w/o sign-up)

Thank you for that, BuffaloHELP! I now aswell know how to do it. I will try it out later, but from what I have seen, it looks pretty simple. The simplest things always make the most difference ;o

Comment/Reply (w/o sign-up)

Thanks for the info buffalo.

The only problem with using the default border styles is that my image was more complicated...but I replicated it by using nested spans, each with their own color solid border. Slightly convaluted, buy hey--it works.\

Good call on the menu classes as well.

I'm slowly ironing out the problems with this template. Your assistance is very much apprecaited (now it's time for a new problem topic ;P)

Comment/Reply (w/o sign-up)

Thanks again to everyone for your help, it's very much appreciated.

This particular issue pertains to: http://www.facesofwar.org/gallery.html

I'm using a fluid layout with separate style sheets for the following resolutions: 800x600, 1024x768, and 1280x960. All of the pages render correctly on Firefox and Safari. Unfortunately, for no reason that I can figure out, internet explorer refuses to restrict the width of the div tag containing text in the 800x600 and 1024x768 versions of the gallery page. (Yes, I know that i.e. doesn't natively support the css max-width/min-width commands, but I'm getting around it with a javascript). Furthermore, the image size for the thumbnails on that page isn't always correctly restricted either (but I verified that the correct style sheet *is* getting applied). The odd part is that it works 100% fine in the 1280x960 version. And, besides the differing measurements, all the style sheets are completely identical.

This one has me really stumped.

The 800x600 style sheet is at: http://www.facesofwar.org/templates/facesofwar/css/800.css
The 1024x768 style sheet is at: http://www.facesofwar.org/templates/facesofwar/css/1024.css
The 1280x960 style sheet is at: http://www.facesofwar.org/templates/facesofwar/css/1280.css

If anyone can help me figure out what the hell is going on I'd be *exceedingly* grateful.

Comment/Reply (w/o sign-up)

This is one of you paragrafs i looked at 1024 version..

when i searched your CSS at /templates/facesofwar/css/1024.css i didn't find any CSS description for
giDescription class..

maybe that is the problem?!

Comment/Reply (w/o sign-up)

The gallery page includes an embeded version of Menalto's Gallery2. As such, it loads its own stylesheets as well (http://www.facesofwar.org/gallery/modules/colorpack/packs/bluebottle/color.css and http://www.facesofwar.org/gallery/themes/matrix/theme.css).

However, the global stylesheets (for the site) are loaded afterwards...so they should take presidence.

Comment/Reply (w/o sign-up)

I narrowed the problem down to the javascript stylesheet chooser I was using. I changed to a different one, and now that issue is gone. Ofcourse there now are other problems, but c'est la vie.

Comment/Reply (w/o sign-up)