I found (a while back) that, in IE 5+, when using tables, if you put all
of your cell code on a single line (i.e.: <td height="140">What's going
on!?</td>) that it would include another line afer the content in the
cell. However, by adding a line break (i.e.: <td height="140">What's
going on!?</td><br />) it would take out the additional space and that
it would appear correctly in the various browsers as well (IE, NS, MZ,
etc.). Now, this rendering may have changed in the other browsers since
then (haven't tested in a while), but in IE it still acts the same.
Cutter
Nando wrote:
> Woa! This was a real learning experience!
>
> I got turned on to building everything fully XHTML compliant, and so i
> thought, naturally, that i should be using an XHTML doctype. Right?
>
> Turns out that the ONLY doctype i could get to "work" properly in this
> case was the old standard: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML
> 4.01 Transitional//EN">
>
> What's even more ... interesting ... or weird if you like, is that in
> the end, i found it wasn't the CSS styles that were throwing the
> height out of wack as i had assumed ... it was just the height
> attribute on a TD tag.
>
> in every other doctype that i tried,
>
> <td height="140">What's going on!?</td>
>
> would render 160 pixels high in IE. (and empty of all content the td
> would render 140px high).
>
> <sigh>
>
> Anyone have any suggestions how to move forward here? I've been trying
> to shift out of using tables entirely but i keep getting snagged on
> one browser or another, and have to fall back on using them to keep
> layout elements in place and my clients from thinking i'm an idiot.
>
>
>
> On Fri, 20 Aug 2004 15:23:29 -0400, Sandy Clark <[EMAIL PROTECTED]>
> wrote:
> > Check to see what rendering mode you are working in. If it is
> quirks mode,
> > that can be the problem.
> >
> > If it is quirks mode than make sure you use a doctype that forces
> standards
> > mode.
> > The xml prolog will send IE6 into quirks mode.
> >
> > To check, type _javascript_:alert(document.compatMode) into your
> address bar.
> > If it comes back with CSS1Compat then you are in standards mode.
> >
> > A good explanation of the document types and the rendering modes they
> > trigger can be found at
> > http://www.hut.fi/u/hsivonen/doctype.html
> >
> > Sandy Clark
> > Now offering 4 days Hands on CSS training October 11-14th.
> Rockville, MD.
> > For more information go to:
> > http://www.teratech.com/training/oc_classes.cfm#css
> >
> > ________________________________
> >
> > From: Nando [mailto:[EMAIL PROTECTED]
> > Sent: Friday, August 20, 2004 2:58 PM
> > To: CF-Talk
> > Subject: Does IE6 in XP render differently?
> >
> >
> >
> >
> > I ran across an oddity the other day ... I develop on Win2000 and
> > usually check page layouts in IE5, 5.5 and 6, Netscape, Firefox, and
> > on a few Mac browsers (depending on the client). A co-worker brought
> > to my attention the fact that a page she had designed was rendering
> > very differently on her XP IE6. Whoops!
> >
> > The offending code seems to be my use of padding, or indeed any type
> > of css sizing (width, margin, padding, height. Something as simple as:
> >
> > <div style="padding-top:20px;">
> > A few words in here
> > </div>
> >
> > within a TD having a height attribute in the tag renders very
> > differently in IE6 on XP (on her machine) than in all the other
> > browsers i'm testing on. At first glance, it seems to indicate that
> > the only way around this is to go back to using spacer gifs (uhhgg!).
> >
> > Before i over-react - has anyone else run into this before? Can you
> > give me an idea of the scope of the problem?
> >
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
