since a few days there seems to be a problem with a audio player script (flash + javascript) on one of our pages that NEVER occured before and I changed absolutely nothing in the code (it has worked for a few years now) that could cause this issue.
We bought the audio player script a few years ago, and again, until a few days ago, it worked perfectly.
The error also behaves very strange. Let me explain...:
The page is www.imatunes.de . You can see these small audio players on each article there.
Feel free to check out the code, got nothing to hide there.
My coworkers told me, that suddenly nothing happened if they clicked on the "Play" buttons. Normally, the script should start the flash player, which plays an audio file.
Now comes the "somehow" strange part:
My coworkers are all using Google Chrome. When they open the page in Chrome and click on a "Play" button, the JavaScript console throws the following error:
"Error on calling method on NPObject".
Googling that error says it has to do something with actionscript, cross-domain policies and such. But the error will get stranger...:
I'm using Firefox, and there it works FLAWLESS. But it also works on MY Google Chrome flawless, so it's very hard to debug (that's why I'm here to ask).
My coworkers also tried it on their home PCs, also running Google Chrome and such, and it also doesn't work there.
Now comes the "very" strange part:
When they get this error and reload the page via the browser controls (F5 or the reload button), it still won't work.
But if they browse around the page or just click on the logo in the header (which basically takes them to the home page again), the script magically works.
And on every other page except for the home page, it will work on first try.
As I said before, this started a few days ago - before that, everything worked just fine. And I really didn't change anything in the code.
So regarding the fact that it works after they browse around the page and return to the home page, it somehow seems like some sort of caching error.
I really don't know how I could debug this, or what to do.
Thank your for every possible help in advance!
Related
I'm trying to build an app using Intel XDK, and I'm running into problems. Things were going well at first, but this morning I was prompted to update XDK, and now my app isn't working.
My login page works fine, and the resulting page with links to various pages in the app work. But when I click a link, the page loads, but is blank, and then I get a JS alert saying:
"It appears you have more than one script tag for cordova.js. There can only be one!"
I found the tag and commented it out to see what would happen, and the only thing that changed was I didn't get the alert. The page is still blank. The only coding I've done was the login script on the index page, so I don't know why it broke. I tried restarting the program, and even recreating the app, and it's doing the same thing. Any ideas why?
There were a variety of changes to the Emulate tab with the new version. I get the impression you're using the Emulate tab. I recommend that you test with the Debug tab on a real device, it will give more accurate results.
After some experimenting, I've come to realize that the problem was I was using List View buttons to navigate, and I was navigating to a different page altogether. That was causing my problem. I just combined all of the pages into one, and it works fine, now.
If you open this site in chrome, it loads and runs ok but I tried loading it in firefox 19.0.2 and I keep getting a Script error asking me if I want to continue or stop. After doing some searching around I found the about:config setting, but that doesn't help. I installed firebug and I see an error about "Permission denied to access property 'toString'" but I have no clue as to what it wants or needs. And the weird part is that if you go to another page in the same site like this one it works just fine. I'm clueless as to what it can be, so any help is much appreciated.
Not a duplicate of this, since it happens on one page but not the other and they both run the same exact code. just that one loads a bit more data than the other. More than anything I'm wondering if its the amount of facebook likes on one page?
When you try to hit play button, you will get a JavaScript error in console in both Chrome and Firefox "TypeError: player is undefined". I tried it and the same error appeared in both console logs. It is and error in the page itself.
I opened it in my firefox browser and it works fine. So it may be there is an add-on which did this error. Try to disable your installed add-ons from (firefox --> add-ons) and reload the page again. If it loads fine then you can enable your add-ons one by one to check which one causes this problem.
Hi I have been using Rokstories, a mootools javascript slideshow in Joomla, I am having a very odd problem with Rokstories in IE . I have uploaded a temp copy to my server to show everyone.
If you click on my link in IE , the page loads and Rokstories works as normal, sliding from left to right every few seconds......click one of the other menu links, then go back to the home page and Rokstories does something very odd, the dots move along to say that it is going between slides, but the actual slide stays put and dont move.
If you clear your cache and reload the page it works fine again until you browse to another menu item and come back, then the problem starts again.
I have tested this with IE8 and get the problem, I have also tried it in Chrome & Firefox and done see a problem.
http://www.key4design.co.uk/test/index.php
The first thing I notice (apart from the Google Maps API key alert) is that IE throws an error:
Line: 989
Error: 'Cufon' is undefined
Looking on Chrome/Safari/Firefox all throw up 404 on cufon-yui.js & /plugins/system/Cufon/key4font_400-key4font_700-key4font_italic_400-key4font_600.font.js
Our experience has been the IE will sometimes fail when JS files aren't in cache when it expects them to be. You might want to fix those first.
Working on a web application and find the Firefox error console to be indispensable.
However I recently upgraded to FF 4 and now when I click errors in the console, the source code doesn't come up like it used to. Not sure it's related to the upgrade but timing is about right.
I've looked over about:config options, made sure the console is enabled, etc. Spent a long time with google trying to find someone else with this problem... nothing.
I get the "hand" cursor when hovering over the URL as if clicking it will do what I expect. However, nothing at all happens. Nada.
I've looked around for hidden windows and even tiny ones but can't find anything...
Any ideas?
Well, I can't exactly figure out why this is happening, but I did find that it only happens when I have the Error Console window on a different display as the main window. I use 2 displays to make debugging easier and moving the error console window to the main display makes it work again.
On a Mac, FWIW.
I have written a word game using HTML5 canvas tag and a little bit of audio. I developed the application on the chrome web browser on a linux system. Recently during the testing phase it was tried on safari 5.0.3 on Mac and the webpage froze. Not just the canvas element, but interactive element on the page froze. I have at some times experienced this problem on google chrome when I was developing but since the console did not throw any error before this happened, I did not give it much credence. Now as per requirements I am supposed to support both chrome and safari but this dismal performance on safari has left me shocked and I cannot see what error can be thrown which might lead to such a situation. Worse yet the CPU usage on using this application peaks to 70-80percent on my 2yr old macbook running ubuntu... I can only but pity the person who uses mac to operate this app, which undoubtedly is a heavier OS. Could someone help me out with a place I can start with to find out what exactly is causing this issue.
I have run profiles on this webapp on google chromes console and noticed that in the heap spanshot value increases steadily with the playing of the game, specifically (root) value which jumps up by 900 counts. Any help would be very appreciated!
Thanks
EDIT: I don't know if this helps, but I have noticed that even on refreshing the page after the app becomes unresponsive the page reloads and I am still not able to interact with the page elements but the tab scroll bar continues to work and I can see my application window completely. So to summaries the tab stops accepting any sort of user interaction inside the page.
Edit2: Nop. It doesn't work still... The app crashes on double click on the canvas element. The console is not throwing any errors either! =/ I have noticed this problem is isolated only to safari!
Edit3: Okay, so I performed some other tests today. I isolated the HTML5 widget and its HTML data only and ran it on safari locally to reproduce the error. Alas it works well! So I tried playing the game from my server without Facebook integration, and it works fine again! So The issue crops up only on safari on MAC OSX, while the widget is on Facebook canvas as a Facebook application. I am very hard-pressed to come up with a reduced test case scenario for this app... =/ It gets weirder, the game works well on safari for windows. Also after the tab freezes the other tabs continue to be responsive and well working. This tab too closes on clicking the close button and stuff, but if I load another page on this same tab after its frozen the page loads in the tab canvas, but I cannot interact with it. Not even google.com! So I am sure there is no bug with my game but its a safari bug... Will soon file a bug report, thanks for all the help people... :)
What you should do, in one sentence: Reproduce the problem with as little code as possible.
Start removing parts of your app until you find nothing that can be removed while still preserving the error. Start by throwing out external resources (css, images, etc) and leave just the html and javascript. Try removing the audio. Try removing as much gaming logic as possible. Try removing all user input code.
If this truly is a bug in Safari itself and not in your code, it should be possible to create a very small code example. Until you have that, saying "my web app doesn't work in safari", without any details or examples, will get you nowhere.