HTML Issue: Firefox inserting break after image - FRUSTRATED! [Archive]

View Full Version : HTML Issue: Firefox inserting break after image - FRUSTRATED!

FW-Mike

04-06-2007, 04:59 PM

I've been working on getting rid of the break under the top two image columns for a while now and can't quite figure it out. Anyone? In MSIE it displays perfectly.

Link:
http://www.forgedweb.com/stoke_07/website/our_philosophy.php

Relevant code:

<table width="860" align="center" cellpadding="0" cellspacing="0" border="0">
<tr>
<td colspan="3" style="background-color:#000000"><img src="images/layout/header-main.gif" usemap="#header_map" border="0"></td>
</tr>
<tr>
<td width="96" style="background-color:#000000"><img src="images/layout/header-left.gif"></td>
<td width="206" style="background-color:#000000"><img src="images/layout/pages/header-page_name.gif"></td>
<td width="558" style="background-color:#000000"><img src="images/layout/header-right.gif"></td>
</tr>

FW-Mike

04-06-2007, 07:22 PM

I STILL cannot figure this out!

Engelmacher

04-06-2007, 07:37 PM

You're using a whole lot of JavaScript to do a whole lot of nothing.

FW-Mike

04-06-2007, 07:44 PM

I am not sure what you mean in that? The black CSS was made to help me see what was going on

FW-Mike

04-06-2007, 07:51 PM

Huh, removing <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> fixed it

Engelmacher

04-06-2007, 07:58 PM

I am not sure what you mean in that?

I mean you should probably pay someone who knows what they're doing to handle this for you because you are making a spectacularly unmaintainable mess.

FW-Mike

04-06-2007, 08:35 PM

I mean you should probably pay someone who knows what they're doing to handle this for you because you are making a spectacularly unmaintainable mess.
Helpful.

I've been doing web development for 9 years and coded this website in my editor along with the PHP portion. Not seeing what your comment pertained != ability

Please don't post any further in this thread.

drhowarddrfine

04-07-2007, 12:24 AM

Removing the doctype was the worst thing to do. Now you are running in 'quirks mode' and you won't get IE to attempt to perform like other modern browsers. Put the doctype back in so we can see what' wrong.

If your code works in IE but not Firefox, then your code is wrong. We have to get it working in Firefox and then adjust for IEs quirks and bugs which is what you were seeing before.

Jay August

04-09-2007, 07:13 PM

Huh, removing <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> fixed it
I've been doing web development for 9 years
Hard to believe mate. After nine years you should REALLY know removing the doctype is one of the stupidest things to do, just as using tables for positioning images.

horizon

04-09-2007, 07:16 PM

you should REALLY know removing the doctype is one of the stupidest things to do

Perhaps the issue was about using a pre-configured web programming software (such as: Macromedia Dreamweaver - which automatically adds this line on top of every HTML files once generated) but I could be wrong. ;)

IAIHMB

04-10-2007, 08:34 AM

The space below the images was descender space which could have been removed by setting the "vertical-align" of the IMG elements on lines 12, 15, 16, 17, and 62 to "bottom".

stdunbar

04-10-2007, 01:02 PM

I'd encourage you to have valid HTML and CSS when running across issues like this. A quick check (http://validator.w3.org/check?uri=http%3A%2F%2Fwww.forgedweb.com%2Fstoke_07%2Fwebsite%2Four_philosophy.php&charset=%28detect+automatically%29&doctype=XHTML+1.0+Strict) with a forced DOCTYPE (not the best design) shows 47 errors. Alot of times these errors are just annoying things but I have found that if my HMTL and CSS both validate then I have a better time working across the different browsers.

bqinternet

04-10-2007, 10:45 PM

I've been doing web development for 9 years and coded this website in my editor along with the PHP portion. Not seeing what your comment pertained != ability

Please don't post any further in this thread.

While the other poster may have been a little blunt, he's absolutely correct. I would recommend reading up a bit more on the workings of CSS and modern design concepts, and also validating your HTML against the DTDs that your doctype header claims to use. A lot has changed in 9 years!