ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

I just upgraded to FireFox 22.0, and now I get a Javascript error (Error: Illegal operation on WrappedNative prototype object). What can I do?

  • 21 პასუხი
  • 97 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 1 ნახვა
  • ბოლოს გამოეხმაურა smartmedia

I just upgraded to FireFox 22.0, and am now getting a bunch of Javascript error pop-ups when I try to sue Gmail. The error message is: Error: Illegal operation on WrappedNative prototype object

I just upgraded to FireFox 22.0, and am now getting a bunch of Javascript error pop-ups when I try to sue Gmail. The error message is: Error: Illegal operation on WrappedNative prototype object

გადაწყვეტა შერჩეულია

'Disable your add-ons and add them one by one (each requiring a restart). If you have some sort of downloader add-on, this can be conflicting with your java/web browser. Hope this helps.'

პასუხის ნახვა სრულად 👍 5

ყველა პასუხი (20)

When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.

(1) Bypass Firefox's Cache

Use Ctrl+Shift+r to reload the page fresh from the server.

Alternately, you also can clear Firefox's cache completely using:

orange Firefox button (or Tools menu) > Options > Advanced

On the Network mini-tab > Cached Web Content : "Clear Now"

If you have a large hard drive, this might take a few minutes.

(2) Remove the site's cookies (save any pending work first). While viewing a page on the site:

  • right-click and choose View Page Info > Security > "View Cookies"
  • Alt+t (open the classic Tools menu) > Page Info > Security > "View Cookies"

In the dialog that opens, you can remove your Google cookies individually.

Then try reloading the page. Does that help?

If the above doesn't work, could you check for extension updates here:

orange Firefox button (or Tools menu) > Add-ons > Extensions category

click the "gear" icon > Check for Updates


If the problem continues, one of your extensions might not have been updated for API changes in Firefox 22. You can disable ALL nonessential extensions on the above tab, or try Firefox's Safe Mode to test the theory.

Firefox's Safe Mode is a standard diagnostic tool to bypass interference by extensions (and some custom settings). More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using

Help > Restart with Add-ons Disabled

In the dialog, click "Start in Safe Mode" (not Reset)

Any difference?

I had the same problem and going through the steps you've outlined, I found the faulty extension - CloudMagic - just wanted to let you know. I have just sent them an email about it which hopefully will result if the extension to be fixed. FYI

I have the same Problem when i use the XINHA WYSIWYG Editor. http://xinha.webfactional.com/

Save mode and clearing the cache does not change anything.

I am getting the same error message for every website I visit, sometimes several times in a row for a single site. Very annoying!

Hi heiland, you wrote:

I have the same Problem when i use the XINHA WYSIWYG Editor. http://xinha.webfactional.com/.

Does it depend on which options you specify in the editor? When I try the "Restricted" demo (second button) on this page I don't get any errors: http://xinha.webfactional.com/wiki/Examples.

Hi jazzshrink, did clearing cache and cookies, and/or Safe Mode, make any difference for you?

Thanx for your answer. The example at the XINHA Website works . For the moment I found a workaround (disabling the XINHA CSS plugin)

me too!!!!

I hope they will fix this problem. When I start in a wrong way Mozilla works. But I can't fix it by myself. I wish I could read how ti fix it in my language swedish.

Hi jazzshrink, did clearing cache and cookies, and/or Safe Mode, make any difference for you?

No it didn't. However, I followed the steps described in Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems and eventually identified that one of my extensions was causing the problem. After I deleted it, everything has been fine. Thanks.

ჩასწორების თარიღი: , ავტორი: jazzshrink

No, it's not available in swedish.

Thanks for the help. Disabling the add-ons and then adding them back in one at a time found the problem.

შერჩეული გადაწყვეტა

'Disable your add-ons and add them one by one (each requiring a restart). If you have some sort of downloader add-on, this can be conflicting with your java/web browser. Hope this helps.'

Castellano: Instalo, desinstalo, vuelvo a instalar, saco los plugins. Y nada. Primero desactivé el youtube downloader y luego los plugins de java, y luego los demás. Siempre me vuelve a poner el cartelito de "Aplicación Javascript: Error: illegal operation on WrappedNative prototype object"

Mejor solución encontrada: Volver al Firefox 3.6 que anda muy bien y que además tiene un caché mas amigable. No hay lo que hacer. El FF3.6 funciona mejor que el FF22.

English: Install, uninstall, and reinstall, desactivate the plugins. First the youtube downloader, after it the others. And nothing. I always get back the little message: "Application Javascript: Error: illegal operation on WrappedNative prototype object "

Best solution found: Return to Firefox 3.6 that is doing very well and also has a more friendly cache. No way. The FF3.6 works better than the FF22.

ჩასწორების თარიღი: , ავტორი: lalomaverde

I have the same problem +

Ever since I upgraded Firefox to 22.0, I have the same problem - "Illegal operation on WrappedNative prototype object" Egads folks, check your product before releasing it. gggggrrrrrrr

Also, there appears to be a long standing problem with Firefox that hasn't been fixed a.k.a memory leak. Firefox keeps using more and more memory and the browser has to be restarted. Why isn't this fixed?

Hi see3ducks, this error seems to be caused by Firefox 22 removing something that some add-ons expect to find. Although add-on developers can learn out about upcoming changes months in advance, not all of them have time to stay on top of them and the results of those changes are not always obvious to them. As noted earlier in this thread, the workaround -- until the extension is updated -- is to disable the extension, whichever one it turns out to be.

Regarding memory usage, can you start a new thread with your system information and describe your observations in more detail? The developers regularly make changes to improve performance and memory efficiency, but they can't account for all scenarios and additional data is always useful.

https://support.mozilla.org/questions/new/desktop/fix-problems

For me the problem extension was "Videos at a Glance 0.79" (10218 no longer on Addons site) even though it was using YouTube where I got the error. In other places "FB PhotoTheater Killer" extension. Others in this thread had a problem with "You tube downloader video 1.3", or "CloudMagic". There were two users who said that they removed an extension, but failed to mention the extension, which is not really very helpful to many others who might have that extension. Please provide details so that others may be helped as well.

Not likely to be the case here, but proper answers might further help to narrow down problems where combinations of extensions may cause a problem like when one person finds they have two extensions mentioned and that disabling either of them would solve a problem which is information that an extension author may find really useful as well as users who figure might not have a problem giving up one of them until problems are fixed.

As far as the actual problem this may or may not shed some light for a developer. jquery - Illegal operation on WrappedNative prototype object - Stack Overflow http://stackoverflow.com/questions/5140156/illegal-operation-on-wrappednative-prototype-object

ჩასწორების თარიღი: , ავტორი: David McRitchie

This is likely a problem with (re)using a function or object name that was previously unused, but now is being used in the current JavaScript version and thus is a reserved variable name and can no longer be used. Easiest would be to check the files and edit the variable name to something different (i.e. add a number or change the case).

  1. 1
  2. 2