Welcome to the MacNN Forums.

macvillage.net · Feb 24, 2002, 09:20 AM

I am working on a new layout which now works with all major browsers but iCab. The URL is as follows:
http://macvillage.net/news/articles/...31729879.shtml

Any help with bringing the page 100% to iCab would be greatly appreciated. I am aware that iCab doesn't like <Font> tags, but that is not a concern right now. I am not so concerned with "making iCab happy" but making "iCab users happy" I try to keep all pages working with all browsers, but iCab is being stuborn. Right now it works with any other browser that I have tested but iCab, so any help bringing compatibility without making any other browser act odd would be a great help.

ReggieX · Feb 26, 2002, 10:01 PM

NEVER put <P> tags around images

I'm having a look at it now, I'll let you know what I can do. I love a challenge.

Reg

ReggieX · Feb 26, 2002, 10:17 PM

Easy fix:

change this:
<TD ALIGN=right VALIGN=top WIDTH=115 HEIGHT="100%">
<P ALIGN=left><IMG SRC="http://images.accettura.com/macvillagenet/header_angle.jpg" WIDTH=115 HEIGHT=115 BORDER=0 ALIGN=top></P>
</TD>
<TD VALIGN=top WIDTH="100%" HEIGHT="100%">
<P><TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" HEIGHT=20>
<TR>

to this:

<TD ALIGN=right VALIGN=top WIDTH=115 HEIGHT="100%"><IMG SRC="http://images.accettura.com/macvillagenet/header_angle.jpg" WIDTH=115 HEIGHT=115 BORDER=0 ALIGN=top></TD>
<TD VALIGN=top WIDTH="100%" HEIGHT="100%">
<TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" HEIGHT=20>
<TR>

The thing you need to do most is to get rid of the <P> tags around all the <TABLE> and <IMAGE> tags.

Rainy Day · Mar 7, 2002, 02:30 AM

Actually, making iCab smile isn't all that hard a thing to do, and doing so makes you code your HTML closer to spec, so that means your code should work better across all browsers. Click on the iCab frownie face to see its error report. Double click on an error item to see it in the source code.

I am aware that iCab doesn't like <Font> tags, but that is not a concern right now.

iCab doesn't have a problem with <font> tags if you use:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

It only dislikes <Font> tags when iCab is thinking in HTML 4.0.

macvillage.net · Mar 7, 2002, 07:03 AM

Thanks. That is in the works to be fixed, I guess I worded that wrong, I know it will like them when HTML Doctype is set lower.... That was my mistake. I just wanted to hear something other than "fix your font tags" when that is not the issue at hand.

Right now the issue at hand is that the blue bar on the top of the screen extends down more than 20 pixels. That is basically all that remains of layout errors, other than that it is just cleaning up the code a bit and some backend work (that is when the doctype bug will be corrected).

Rainy Day · Mar 7, 2002, 12:31 PM

Originally posted by macvillage.net:
<STRONG>I just wanted to hear something other than "fix your font tags" when that is not the issue at hand.</STRONG>

Well, you really should convert to CSS... for so many reasons... but you already know that, i'm sure... and when you do convert, you'll be really glad you did. Then your <font> and <center> tags go away, as do the <body> attributes you're using. That's about 70% of iCab's complaints about your page. The rest are missing closing tags, some IE specific (i.e. non-HTML) attributes to certain tags, and of course a bunch of ampersands which should be expressed as &amp; (even in URL's, btw).

Originally posted by macvillage.net:
<STRONG>Right now the issue at hand is that the blue bar on the top of the screen extends down more than 20 pixels. That is basically all that remains of layout errors, other than that it is just cleaning up the code a bit and some backend work (that is when the doctype bug will be corrected).</STRONG>

I'm not sure i'm seeing the problem here?

Of course iCab is the only browser i'm using to look at you page, so maybe what i'm seeing isn't what's intended?

[ 03-07-2002: Message edited by: Rainy Day ]

macvillage.net · Mar 7, 2002, 02:40 PM

Your post is dated about a half hour after I fixed that bug... thanks anyway.

The page will most likely be converted for CSS, though that may not be in the original release but an update.