The problem is not related to the fact that Chrome is an early Beta but rather that it uses the Webkit Rendering Engine, as does Safari. The WRE resolves complex menus differently to the method deployed by IE, Firefox and Opera.

WebStyle 4 by default creates menu-rendering code that conforms to the same standards as used by IE, Firefox and Opera. This means that WS4 menus display correctly in these browsers but incorrectly in browsers that are based on WRE, such as Safari and Chrome.

The key difference is that the standard used by IE, Firefox and Opera renders menus using the "absolute" location whereas the WRE as used by Safari and Chrome renders menus using the "fixed" location.

A possible work-a-round for this problem would be to ask a question within the document.write statement. In simple English the question would read something like this: -

IF the browser is WRE based THEN menu positions are fixed ELSE menu positions are absolute.

In a real website that uses WS4 the real code may read something like the following: -

if {SAF}
document.write(".filename_menu {z-index:999;border-color:#a5c7db;border-style:solid;border-width:"+bd+"px 0px "+bd+"px 0px;background-color:#185a99;position:fixed;left:0px;top:0px;visi bility:hidden;}");
else
document.write(".filename_menu {z-index:999;border-color:#a5c7db;border-style:solid;border-width:"+bd+"px 0px "+bd+"px 0px;background-color:#185a99;position:absolute;left:0px;top:0px;v isibility:hidden;}");

In most cases this modification to the WS4 generated code will enable complex menus to be displayed correctly in IE, Firefox, Opera, Safari and Chrome.

If you implement this fix will you please post your results to this thread so that we can see how successful (or not) this fix is.

T.