RE: off topic but if anyone feels like lending a helping hand it would be much appreciated

dude...Jon, you are the man!  That's exactly what I needed to know.

>  -----Original Message-----
> From: 	Jon Haworth [mailto:JHaworth@witanjardine.co.uk] 
> Sent:	Friday, May 04, 2001 12:04 PM
> To:	'Michael Stevens'; W3C Mailing List
> Subject:	RE: off topic but if anyone feels like lending a helping
> hand it would be much appreciated
> 
> IIRC Netscape 4.x only allows frames in a grid - not sure of the size but
> I think it's 5px intervals. If you try and put a frame in between two
> intervals NS will move it to the closest gridline.
> 
> BTW, two excellent lists for this sort of question can be found at (a)
> http://lists.evolt.org/ and (b) http://www.wdvl.com/WDVL/Forum/
> 
> Cheers
> Jon
> 
> 
> 	 -----Original Message-----
> 	From: 	Michael Stevens [mailto:mike@hydro.tokenzone.com] 
> 	Sent:	04 May 2001 16:22
> 	To:	W3C Mailing List
> 	Subject:	off topic but if anyone feels like lending a helping
> hand it would be much appreciated
> 
> 	When opening a precisely sized window that exactly fits the contents
> of the page via JavaScript with a frameset inside I get a small display
> discrepancy between Netscape 4.x and IE (Netscape 6 displays the same as
> IE). 
> 
> 	The frameset is coded as follows:
> 
> 	<frameset rows="39,*,64" frameborder="0" border="0"
> framespacing="0"> 
> 	 <frame name="topFrame" scrolling="no" noresize src="viewer1.htm" >
> 	 <frameset cols="25,*,25" frameborder="0" border="0"
> framespacing="0"> 
> 	  <frame name="leftFrame" scrolling="no" noresize src="viewer2.htm">
> 	  <frame name="mainFrame" scrolling="no" noresize src="viewer3.htm">
> 	  <frame name="rightFrame" scrolling="no" noresize
> src="viewer4.htm">
> 	 </frameset>
> 	 <frame name="bottomFrame" scrolling="no" noresize
> src="viewer5.htm">
> 	</frameset>
> 
> 	This frameset is basically a media content viewer window.  The 39,
> 64 and 25 pixel frames act as borders for the "wild card" frame which
> holds content (dynamically placed using JSP).
> 
> 	The content frame is the one with the problem here (I have also
> tried it with absolute sizes, with identical results.)
> 
> 	So, here's the problem:  In IE and Netscape 6 all of the frames join
> together just as I had hoped and surround the content frame
> seamlessly...BUT in Netscape 4.x I get about 4 pixels added on to the
> right of the content frame with totally blows the effect of the
> surrounding frames being the encapsulating frame which holds the content.
> (if I open the window with 4 less pixels on the width it works great in
> Netscape 4.x but not the others.  Of course I could have two versions
> catered for each circumstance but that's kind of clumsy and slightly less
> efficient than I would like to be...but if that's the only option then
> well...that's the only option.  The strange thing is that this seems to be
> the default of Netscape since I can't find anything that would make it add
> these 4 pixels to the right.  Is there a navigator proprietary attribute
> that could fix this??  I haven't been able to track down anything.
> 
> 	Why use a frameset instead of tables?  Well to keep this "viewer" as
> flexible as possible and allow content to be included from anywhere (i.e.
> video from a streaming server) we need to be able to just dynamically drop
> a URL for the content into the frame.
> 
> 	If anyone else has ever had this problem or knows a better way
> (other than frames) to deal with this (which I would gladly welcome) then
> please let me know...or just send me a link to something that could point
> me in the right direction.  I'm at a loss.
> 
> 	Thanks,
> 
> 	Mike
> 	
> **********************************************************************
> 	'The information included in this Email is of a confidential nature
> and is 
> 	intended only for the addressee. If you are not the intended
> addressee, 
> 	any disclosure, copying or distribution by you is prohibited and may
> be 
> 	unlawful. Disclosure to any party other than the addressee, whether 
> 	inadvertent or otherwise is not intended to waive privilege or
> confidentiality'
> 	
> 	
> **********************************************************************
>