Re: context menu solution, iframe problem still here

huh? ... your iframe tests worked very nicely here main file iframe style=hidden and if a user note is availiable, then it switches it to visible ..nice trick actually i find :) -- "Gabor Hojtsy" <gabor@hojtsy.hu> wrote in message news:012d01c24dbd$fc00be20$0f00000a@developer2... > Hi! > > > Well, I played with a few hours with this thing, trying out some ideas, and > looking through MSDN, and found out the solution to the context menu > problem. > Just in case someone wonders, I write it down here, so if someone plays > with IE6, he knows what to expect. > > There are certain !DOCTYPE declarations switching IE6 to "standard compliant > mode". See this MSDN page for more information: > > http://msdn.microsoft.com/workshop/author/dhtml/reference/objects/doctype.as > p > > Those switches may be logical or not, but the outcoming of them is > that some behaviours of IE are different in standard compliant mode than > in backward compatible mode, as one may guess. > > One of those is that the container for the document is the HTML element, > not the BODY element, so the contents of the body element is not scrolled > (it's fixed into the html element). This means that in standard compliant > mode (which is turned on by a !DOCTYPE used in all the HTML pages in the > CHM) we need to use the HTML element to find out the scrolling distance, > but as it won't work in older IE browsers we need to use the body if > the browser is preIE6. > > This actually fixes the context menu positioning bug, so the only one left > is the iframe problem, for which we were unable to come up with at least a > fix idea. > > The two solution ideas for that problem was > > a) turn on show friendly error messages > b) apply the Service Pack on your IE6 when it comes out > (now it's in beta testing phase) > > If anybody has a better idea besides these two, please do not hesitate to > write in ;)) > > Goba >