Re: for the thousandth time already....

Thank you so much Marc, Kehvan and Franchesca

Because of your suggestions, I did a lot of cleaning out of spaces in the
code, the tables on a number of pages are a lot cleaner now. Kehvan, your
suggestion about making the graphic a background in the frame was spot on, I
never thought of that -- or I was avoiding background images altogether
(after a recent burn by Netscape not displaying background images in table
cells). It matched up perfectly in Netscape as a background image (then
split in Explorer). I have to leave the lesser evil of a single-pixel split
for now, but will be much farther ahead the next time.

Thanks again.

Maggie.

-----Original Message-----
From: Kehvan M. Zydhek <kehvan(at)zydhek.net>
To: Maggie Carr <m.a.carr(at)decaelo.com>; hwg-graphics(at)hwg.org
<hwg-graphics(at)hwg.org>
Date: June 22, 2001 8:49 PM
Subject: Re: for the thousandth time already....


:Maggie,
:
:Marc's advise notwithstanding, you mentioned frames specifically in your
:post. Netscape 4.x and below cannot to frames to pixel-perfect resolution,
:no matter how hard you try. You can get it to look about right, but it
won't
:be perfect. That's because Netscape takes the pixel width (or height,
:depending) you give it, divides that into a percentage based on the
:available rendering window's size, rounds that percentage to an integer,
:then calculates it BACK to pixels (again, rounded to an integer). The
result
:is gaps in frames. To watch this process in action, resize the browser
along
:the same axis as the frames (in this case, since the frames are vertical,
:resize the browser's width). Do it in small jumps of just a few pixels each
:time. After Netscape refreshes and reloads the page, you'll see the frame
:gap get bigger or smaller (including overlapping a bit) depending on the
:calculations it does. I've found in tests that Netscape renders my frames
:with a plus or minus of about 10 pixels of where I wanted it.
:
:One possible alternative, if feasable, is if the image is a background
image
:for the frame itself (and is not loaded using an <.img src> tag), then you
:can experiment with making the background image larger than needed but
:leaving frame 2's image as-is, that way the gap may not be visible as much
:when the frames are put together.
:
:Netscape 6 does not have this problem.
:
:Hope this helps,
:Kehvan

HWG: hwg-graphics mailing list archives, maintained by Webmasters @ IWA