have a javascript code to exec on a page - all works fine in Firefox, IE, Chrome but does not work in Opera 10+.
Strange is that this javascript works fine in previous versions of Opera (9.xx is fine) and even more strange is that when I lunch Dragonfly on Opera 10+ the javascript works also fine (and Dragonfly does not throw any errors).
Have anyone experienced this behavior and found any solution/workaround?
As the js code is quite complicated, huge and part of it dynamically generated I am not posting any sample of it - my question is just about the behavior and if someone has any experiencies with debuging/resolving.
Thanks,
Jan
It sounds like a bug in Opera's Just In Time (JIT) compilation. I assume that it worked in 10.10 but broke in 10.50 and above. Does it work if you disable this option: opera:config#jit ?
I would very much appreciate a bug report with code - https://bugs.opera.com/wizard/ . If you report the bug number here I can follow up a little bit faster :).
Check this Tools..Preferences..Advanced..Content..Javascript options
Or tools..Quick preferences..ensure "enable Javascript checked"
Or you have overridden these with site preferences or user mode stuff.
I'm typing this in Opera 10.60 with no problems, admittedly not as developer or with Dragonfly running
Try: Tools -> Advanced -> Error Console
Related
Non-Webkit Opera was very specific in some features, so it was usually detected via JavaScript the following way.
However, Opera Next seeps to be almost a Google Chrome clone.
How can I target old Opera and not target Opera Next?
PS: I really do know that browser detection sucks and feature detection rules. But I hope to update the big and running project with a tiny browser-detection-patch rather then to rewrite tons of code into feature-detection paradigm.
I have found the problem source. It was in bad browser detection in that project. If you detect Opera exactly like in the link given in the question, Opera Next is not detected to be Opera, so Old-Opera-Specific code is not executed, and Chrome-Specific-Code runs instead.
!!window.opera; // true in old Opera, false in Opera Next
navigator.userAgent.indexOf("Opera");// ------- the same --------
PS: Fortunately, I have lots of tests on my project, so I can tell that in new Opera things are working exactly as in Google Chrome.
A piece of code that caused problems tried to detect Opera Old AND Opera Next:
/(Opera|OPR)/.test(navigator.userAgent)
Conclusion: Opera migration was made very well, nothing should break in your projects. Do not detect Opera Next and simply treat it as usual Google Chrome.
UPDATE: previous Opera versions had gone from caniuse.com
If you view this page...
http://eastlondondance.org/admin/MozillaProblem/example.php
...you'll find that there are no errors but that the functionality is not working.
The last dropdown is not being populated with options like the other 2. This however works on Safari, Chrome and IE.
What gives? Why isn't it working on Firefox Linux, PC or Mac but is on all other browsers?
Is it a problem with the code or a problem with Firefox?
Any help is much appreciated.
cheers,
George
Firefox is having problems with the variable name of performance. While I'm not certain why this is, renaming this to anything else will allow it to display in firefox. In the example below I renamed it from performance to performancex.
Example: http://benjaminhopkins.co.uk/stackoverflow/firefox.html
From the comments above seems not everyone see the problem? Maybe it could be a extension / plugin causing the issue. Using the developer toolbar and hovering performance firefox reveals the following:
Performance { constructor=Performance,
timing=PerformanceTiming,
navigation=PerformanceNavigation}
I have made a simple embed of slideshare on my site. However, on Internet Explorer, it keeps saying "Loading" and nothing appears. However, in Firefox its almost instant. Please try here using internet explorer.
Or is it just me? It makes use of Flash and Javascript.
What can the problem be?
Thanks all for any hellp
This page works fine in IE9 at least, and the content you say is broken was written in Flash. You might want to watch your HTTP traffic using Fiddler (www.fiddler2.com) and check for script errors using IE's developer tools (hit F12).
I've check it in Chrome, Firefox, IE6/7/8 and they all seem fine. I haven't checked it in Opera or Safari though.
I have some code that I thought I had written so that it would play nice on IE. But apparently it does not. I use IE8 for my testing and get quite frustrated with the built-in debugging 'tool'. I found that firebug has a javascript tool that debugs for IE but I have to click it for every page, wait for it to load and then test my script. Is there a way to make IE ALWAYS load the firebug .js file? I tried searching for way to set up a custom header file for my IE installation but was unsuccessful.
Is there another tool out there that would be better/easier to use? Another way to test scripts for IE compatibility?
IE7 and 8 provided the IE developer toolbar. This is similar to firebug for DOM inspection, script debugging and style tracing.
Edit:
For IE 8, the toolbar is already packaged with the browser:
The Developer Toolbar is not compatible with Internet Explorer 8. Please use the developer tools included with Internet Explorer 8. Press F12 or click the 'Developer Tools' entry in the Tools menu to begin using the tool. Click here for more information on IE8 Developer Tools.
You can also use Visual Studio and attach to the process in question, then just debug in VS. Pretty good debugging tools, and lets you debug IE6 as well.
Try my log4javascript, which is a logging library that works in every major browser, including IE 5 and later.
see my question on title.
note that I understand how to debug javascript in any browsers (including IE 7++) other than IE 6.
IE Developer Toolbar really good to have for any developer.
IE Developer Toolbar
Microsoft script debugger can provide a bit of information.
But in general - it's a pain in * * *.
Last time figured out what's wrong by gradually commenting out javascript code. :D
You can also use firebug lite.
Personally I'm a big fan of FireBug Lite which is perfect for IE.
Firebug is an extension for Firefox, but what happens when you need to test your pages in Internet Explorer, Opera, and Safari?
The solution is Firebug Lite, a
JavaScript file you can insert into
your pages to simulate some Firebug
features in browsers that are not
named "Firefox".
Firebug Lite creates the variable
"firebug" and doesn't affect or
interfere with HTML elements that
aren't created by itself.
Firebug Lite has helped me out quite a lot =)