DIVs Not Working With Firefox - hidden image and scrollbars

[pressurecooker]

Hi,

When using Firefox, my theme for intermediate display is corrupted. FF doesn't understand DIVs and the image gets tucked under the navigation bar and a scrollbar displays.
I have tried just about everything, even editing themes.inc.php although I know I shouldn't. It doesn't respont to any measures.
Here is the link:
http://www.nanotoxic.com/cpg.html

Help please! 

Sorry about the redirect but I may not give out the link as it is...

[Stramm]

NOTE You may download preview or order fullsize version of any image...

doesn't break. Why? I do not know. Maybe someone else...

[morgoth]

Hi,
maybe attribut text-align in the calss .content:

Code Select Expand

.content {style_cpg.css (line 899)
margin-left:auto;
margin-right:auto;
margin-top:25px;
min-height:400px;
padding-left:6px;
position:relative;
text-align:left;
width:924px;
}

[steveeh131047]

Pressurecooker,

Not sure if it helps you, but with all styles disabled on Firefox the intermediate image is still way off to the right of where you want it to be, so I think it's a table issue rather than a CSS issue. The intermediate image is sitting centrally in a very wide "display_media" table cell - I'm guessing it's about 2000px wide.

Steve

[steveeh131047]

Just confirmed that if I change align="center" to align="left" in that <td> tag, it fixes the problem in Firefox.

[steveeh131047]

Also noticed that taking out the "nowrap" in this tag fixes the problem.

W3C manual has this to say about "nowrap":

nowrap [CI]
    Deprecated. When present, this boolean attribute tells visual user agents to disable automatic text wrapping for this cell. Style sheets should be used instead of this attribute to achieve wrapping effects. Note. if used carelessly, this attribute may result in excessively wide cells.

Note the final sentence.

[pressurecooker]

Stramm, morgoth, steveeh131047 thank you for your input.

steveeh131047, you were absolutely right, "nowrap" caused the problem. Much obliged!

Obviously the recent FF update changed the way this browser parses the code because this surprise occured only when I upgraded my FF a couple of days ago.

So the bottomline is simple: get rid of outdated and wrong HTML even though IExplorer is so nice and forgiving 

[steveeh131047]

Pressurecooker,

1) Pleased to be able to help

2) When I "pass on" my grave's headstone will be engraved:

- keep the content in the HTML
- keep the styling in the CSS
- DON'T use tables for layout
- design so that it looks OK in Firefox (or some other standards compliant browser) first, and only then see what "tweaks" might be needed for IE

I might need a big headstone for that last sentence.

[pressurecooker]

 
Forget what I said about IExplorer. Although the layout is working in FF, the site has become absolutely unusable in Explorer. If you could look into the link from my first post, you'll see that everything is messed up and some outrageous scroll bars have now appeared.
Any ideas?

[pressurecooker]

D'oh. Tables in displayimage.php did not break at all. So $template_img_navbar, image display table and filmstrip table were displayed in a row like this
<table><table><table>

That's stupid!!! If you code html and create three tables one followed by another, the result is
<table>
<table>
<table>
innit?

I solved my problem by adding

Code Select Expand

<br clear="all"> after endtable function in themes.inc.php

I know I must not edit this file but I had no other option. I keep all the records of my changes so after an upgrade I will still be able to make those changes again.
I was of better thoughts about Explorer 

[Joachim Müller]

I solved my problem by adding

Code Select Expand

<br clear="all"> after endtable function in themes.inc.php

I know I must not edit this file but I had no other option.

That's utter nonsense. Everything that can be accomplished by editing include/themes.inc.php can be accomplished just as well by editing themes/yourtheme/theme.php. I'm glad that this works for you, but your "recommendation" to others might give them the impression that it's a bright idea to edit that file - it isn't. It really isn't. Absolutely not. You're drawing the false conclusions.