Re: Re: Re: Re: Try this...
But OmniWeb *is* compatible with the web site. I visited it this morning. Half of the problem is that OmniWeb *identifies* itself as itself and does not try to fool the site into thinking its IE or Netscape. The other half is that the site does not even try to send content to a browser it deems unable to handle the content.
I place more blame on Harley's site. They judge a browser worthy of content based only on the name of the browser. There are technical reasons to require a specific browser to view a site (notable examples of this are when developers choose to develop a site using IE specific code--then a Netscape browser can't handle the site). While OmniWeb is capable of handling a lot of code for either IE or Netscape, they are much closer to Netscape in implementation.
The bottom line is that OmniWeb identifies itself as a Mozilla compliant browser BY DEFAULT. Mozilla is the same engine new versions of Netscape use. The fact that Harley ignores this and doesn't even try to send content to a perfectly capable browser is simply LAZY CODING.
OmniWeb is not perfect, but it's creators have very little control over this problem. It all goes back to a lack of accetable web standards and a proliferation of incompatible code on the internet.
Matthew
Originally posted by AlphaTech
Then you wouldn't need to f*ck with the preferences and such just to use it for sites you visit often.
But OmniWeb *is* compatible with the web site. I visited it this morning. Half of the problem is that OmniWeb *identifies* itself as itself and does not try to fool the site into thinking its IE or Netscape. The other half is that the site does not even try to send content to a browser it deems unable to handle the content.
I place more blame on Harley's site. They judge a browser worthy of content based only on the name of the browser. There are technical reasons to require a specific browser to view a site (notable examples of this are when developers choose to develop a site using IE specific code--then a Netscape browser can't handle the site). While OmniWeb is capable of handling a lot of code for either IE or Netscape, they are much closer to Netscape in implementation.
The bottom line is that OmniWeb identifies itself as a Mozilla compliant browser BY DEFAULT. Mozilla is the same engine new versions of Netscape use. The fact that Harley ignores this and doesn't even try to send content to a perfectly capable browser is simply LAZY CODING.
OmniWeb is not perfect, but it's creators have very little control over this problem. It all goes back to a lack of accetable web standards and a proliferation of incompatible code on the internet.
Matthew