We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

FireFox v.22, Mac (Java 7 update 25) calls onload() with applet unkown status ('undefined' instead of 1,2,or 3 - LOADING, READY, or ERROR)

  • 1 resposta
  • 2 têm este problema
  • 1 visualização
  • Última resposta por iamjayakumars

adaj21
adaj21
more options

I have a simple html page that loads an applet. The page's onload() handler checks for the applet's status and if loading it registers an applet load and error handler, if ready it starts using the applet. For more details, check this link 

 http://docs.oracle.com/javase/tutorial/deployment/applet/appletStatus.html

On most machines this works properly. On some Mac machines the applet's status is undefined when the page's onload handler is called. The java console confirms that the applet has been loaded, initialized and started. If I use a self signed jar, on machines that work properly, the onload() handler is only called *after* I answer the security dialog. On the machine that fails, onload() handler is called *before* I answer the security dialog. I iterated through document.applets and found that my applet is found both by name and by id Opened up firefox' debugging tools, there are no errors in the console.

I have a simple html page that loads an applet. The page's onload() handler checks for the applet's status and if loading it registers an applet load and error handler, if ready it starts using the applet. For more details, check this link http://docs.oracle.com/javase/tutorial/deployment/applet/appletStatus.html On most machines this works properly. On some Mac machines the applet's status is undefined when the page's onload handler is called. The java console confirms that the applet has been loaded, initialized and started. If I use a self signed jar, on machines that work properly, the onload() handler is only called *after* I answer the security dialog. On the machine that fails, onload() handler is called *before* I answer the security dialog. I iterated through document.applets and found that my applet is found both by name and by id Opened up firefox' debugging tools, there are no errors in the console.

Todas as respostas (1)

iamjayakumars
iamjayakumars
more options

Hello,

Try Firefox Safe Mode to see if the problem goes away. Safe Mode is a troubleshooting mode, which disables most add-ons.

(If you're not using it, switch to the Default theme.)

  • You can open Firefox 4.0+ in Safe Mode by holding the Shift key when you open the Firefox desktop or Start menu shortcut.
  • Or open the Help menu and click on the Restart with Add-ons Disabled... menu item while Firefox is running.

Once you get the pop-up, just select "'Start in Safe Mode"

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, and you need to figure out which one. Please follow the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article for that.

To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.

Thank you.