Seems opera can not work normally with javascript, does anyone knows how to fix it?
Thanks in advance.
Thanks in advance.
-
-
Re: Opera vs Javascript
"Spijon" <spijon@online. com.ua> wrote in message
news:8dfdf9b1.0 307152243.f4fa8 ff@posting.goog le.com...[color=blue]
> Seems opera can not work normally with javascript, does anyone knows how[/color]
to fix it?[color=blue]
>[/color]
Please be more specific. What exactly is the problem?
JW
-
Re: Opera vs Javascript
Problem is too wide, I've got a lot of javascripts and almost none of
them are displayed correct. IE, Mozilla and FireBird shows them
perfectly. So question is maybe it doesn't support some set tags or some
features. If it does than where can I find such list?
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Comment
-
Re: Opera vs Javascript
Igor Galchevsky wrote:[color=blue]
> Problem is too wide, I've got a lot of javascripts and almost none of
> them are displayed correct.[/color]
Your post would have been a lot more relevant, I would say, if you had
given an url where some of the "javascript " problems exist, can be verified.
IE, Mozilla and FireBird shows them[color=blue]
> perfectly. So question is maybe it doesn't support some set tags or some
> features. If it does than where can I find such list?
>[/color]
Web specifications supported by Opera 7:
Complete support table for CSS1 and CSS2 in Opera 7:
Complete table of ECMAScript support in Opera 7:
Complete table of DOM 2 Core support in Opera 7:
Complete table of DOM 1 HTML support in Opera 7:
Complete table of DOM 2 Events support in Opera 7:
Complete table of DOM 2 Style support in Opera 7:
Complete table of non-standard JavaScript support (soon)
but you should not trust blindly these charts. I personally noticed
there are some exaggerations, imprecisions, lots of bugs and plain
errors in these charts.
DU
---------------------------
Javascript and Browser bugs:
Comment
-
Re: Opera vs Javascript
If the script uses any kind of browser detection, you have to be very
careful, especially with Opera. At one time you could depend on
appName and appVersion to sniff out the browser, but not anymore. If
you use appName to detect Opera you get Microsoft Internet Explorer!
If you go to userAgent on Opera 7.11 you find: Mozilla/4.0(compatible;
MSIE 6.0; Windows NT 5.1) Opera 7.11 [en]. Thus you would have to seek
out Opera in the userAgent to find Opera. For the Microsoft IE6 that
is slightly modified by the ISP MSN, you get an appName of Microsoft
Internet Explorer at least. However the appVersion is 4.0( compatible;
MSIE 6.0; Windows NT 5.1; Net CLR 1.0.3705, MSN 8.0; MSN 8.5; blah
blah. Most browsers give apCodeName as Mozilla. However MSNTV(WebTV)
gives "bowser" instead and this is the most simple way to detect
MSNTV.If you detect the wrong browser, you may get false results
concerning positioning and other "geometry" of the screen. You usually
need to check for document.all and W3C
(document.getEl ementByIdSuppor t).If you are interested in the old
Netscape 4 series browsers, you may also need to check for
document.layers support. IE4 uses document.all. IE5 and 6 use both
document.all and W3C DOMs. Even on the IE6, many still write using the
document.all DOM. Netscape6+ and the Mozillas use the W3C DOM only.
Opera 7.11 still uses both the document.all and the W3C DOM, although
the Opera users are more likely to select the W3C DOM than are IE
users. The point of this is that much older script used simple browser
detection to determine the correct code to use, and this often must be
updated for modern browsers for reasons mentioned above. Failure to do
so can result in all sorts of distortions of the page when viewed on
some browsers. In such a case, the problem is with the code written on
the page - not the IE, Netscape, Opera, etc. browser.
Comment
Comment