|
|
Posted by dorayme on 11/16/42 11:57
In article
<1157425407.479469.77900@i42g2000cwa.googlegroups.com>,
"cwdjrxyz" <spamtrap2@cwdjr.info> wrote:
> dorayme wrote:
> > In article
> > <1157413761.150988.137700@74g2000cwt.googlegroups.com>,
> > "cwdjrxyz" <spamtrap2@cwdjr.info> wrote:
>
> > My test page to show folks is a grab from another context, (which
> > had the encoding you probably mean, I failed to grab it). It
> > seems to be doing what I showed in the pic urls from your
>
> > Anyway, as I am working on the original from which I grabbed the
> > puzzling table I think I did something when cleaning it up and it
> > is now showing up in Safari and Opera as in the others. There is
> > now only some oddness about the test case! I better not stop to
> > investigate for now...and get on with the work.
>
> I think I may have found the problem. See
> http://www.cwdjr.net/test/tabletrouble.html . What I did is explained
> in a comment near the bottom of the source code. It appears that when
> you need more vertical space for the swatch image column than the text
> columns alone would need, a sort of overflow adjustment is made, and it
> is different for different browsers. I removed 2 swatch images to
> correct the problem. You likely could do the same thing by adding more
> text rows or adding some extra breaks or something to use more vertical
> space between the text rows. Excuse the images. I did not have a link
> for yours, so I just threw in the first things that came to mind, but
> kept the image dimensions the same as you used. The page now views
> about the same on most recent versions of Firefox, Mozilla, Netscape,
> Opera, and IE6 on Windows XP. Of course different text size defaults on
> the different browsers make some difference. Even old Netscape 4.8
> works except all of the lines in the table are missing.
Thank you for taking the trouble cwdjrxyz... I will have to come
back to this later. It was interesting to see the way different
browsers cope. Love your frog! (I did not include any actual pics
for the test html).
The practical problem is not severe in fact I realise now. In the
real context, the problem is hidden because the table is in a
page where it has a naturally restricted (not author imposed)
width - in other words, there is other stuff and the prob might
only appear on improbably big screens then. You can see all
behaving better in Opera and Safari as you restrict the width of
the browser window even if you have as many as four chipmunks on
the right.
--
dorayme
Navigation:
[Reply to this message]
|