4.5 beta 3 (v488) problem

Karl Kuehn larkost at softhome.net
Wed Jul 16 13:09:02 PDT 2003


	Actually, the JavaScript that generates the frameset for the page 
makes the generalization that you either use Netscape or IE proprietary 
features, namely layers or the document.all features. Since OmniWeb 
sticks more to the standards in this case, they don't exist in either 
category, and so they fall right out of the logic.
	If the page designer had thought about it, they would have established 
a single test, and defaulted to the other. But since they test for both 
(in a silly way), they fail for both, and are not picking up this case. 
OmniWeb is accurately displaying what the logic on the page says. Here 
is the relevant code:

if (ie)
	document.writeln("<frameset frameborder=\"0\" framespacing=\"0\" 
rows=\"95,*,44\">");
if (ns){
	document.writeln("<frameset frameborder=\"0\" border=\"0\" 
framespacing=\"0\" rows=\"96,*,48\">");	function redraw(){
		window.location.reload()
	}
}

Simplifying it to (I would go even simpler):

var ns=(document.layers)?true:false;
if (ns){
	document.writeln("<frameset frameborder=\"0\" border=\"0\" 
framespacing=\"0\" rows=\"96,*,48\">");	function redraw(){
		window.location.reload()
	}
} else {
	document.writeln("<frameset frameborder=\"0\" framespacing=\"0\" 
rows=\"95,*,44\">");
}

	Lets it work in every case.

		Karl Kuehn
			larkost at softhome.net

On Wednesday, July 16, 2003, at 03:42 PM, Dr Laurance D Jacobs wrote:

> https://www.h-l.co.uk/live/defaultL.htm  - tells me title page and 
> then gives up.
> ldj




More information about the OmniWeb-l mailing list