Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → 2.0 Branch
Please take a look in the following document: http://jdk6.java.net/plugin2/liveconnect/#JS_J_THREADING chapter 2.5 describes the threading model in detail.
today i've installed firefox 5 and run the above test case again with the following results: 1. onload: href & button are enabled, could trigger actions ONLY from the button! 2. applet call made after onload is finnished: If I trigger the applet call from href, I'm always able to reproduce the problem If I trigger the applet call from a button, I wasn't able to reproduce the problem It seems that the bug still appears in Firefox 5, however the behavior changed from Firefox 4 to Firefox 5
Severity: major → normal
Version: 2.0 Branch → 5 Branch
anyone working on this topic?
Out of curiosity, how is this behaving in Google Chrome?
I ll create a corresponding entry in the Java Bug Database and will inform you about the results here
The important point here is: the browser thread does block waiting for a call to plugins to return. But if the plugin spins the event loop (which is a terrible idea, but many plugins do it anyway), then the browser can reenter through events such as additional mousemoves/mouseclicks or even networking events.
I'm marking this bug as WONTFIX per bug #1269807. For more information see - https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.