Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: incrediBILL
The oddity shows up when I have an image that is sliced up beyond one vertical strip -- and then held together either with table cells or just coded inline using <BR> tags.
Even though many different code configurations will give a perfectly matched up image in MISE, Netscape often insists on adding an extra one pixel gap between the last two horizontal strips.
Sometimes I can fix this by eliminating all hard returns in the code -- seems that Netscape doesn't always ignore returns and can mistake them for a <BR>.
Sometimes I can eliminate the table and just list all the pieces inline with appropriate breaks. And sometimes the reverse needs to happen -- inline pieces show the gap but a table will hold the pieces together without a seam.
And in one case, I can't think of anymore options, so Netscape users get the gap and Explorer users see the seamless image.
Anyone else wrestling with this? Any insights?
When in doubt, find a page that has strip graphics and have a look at the source.
Netscape interpts a return as a space except when overriden by code where a space isn't applicable. Quite common among browsers - opera does it too.