Closed Bug 834918 Opened 9 years ago Closed 6 years ago
Plugins in chrome content should not be click-to-play
User Agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17 Steps to reproduce: I have an extension using java (RecipeFox: https://addons.mozilla.org/en-US/developers/addon/recipefox). When Oracle raised the security level to High in java 7 update 11 it worked fine, because java popped up a dialog requesting to run java in chrome://browser... But when Mozilla later moved the java 7 update 11 plugin to the Click-to-Play list, it doesn't work anymore. Is there any way to enable java in extensions while it is in the Click-to-Play list?
Component: Untriaged → Plug-ins
Product: Firefox → Core
I assume this addon is not inserting Java into the page, but instead using an embed/object in some background element? I guess for such things we should be able to differentiate whether it's in-page or in some addon-/browser-specific element and probably assume user-trust there (i.e. not block it).
Yes, I'm using an embedded java object as suggest here: https://bugzilla.mozilla.org/show_bug.cgi?id=748343#c47 after the java keyword was dropped in Firefox 16. Frank
Status: UNCONFIRMED → NEW
Ever confirmed: true
nsObjectLoadingContent::ShouldPlay / ShouldPreview could be bypassed for chrome content. In the meantime, with chrome privileges you should be able to force the plugin to play with: > obj.QueryInterface(Components.interfaces.nsIObjectLoadingContent).playPlugin() Similarly, you can test to see if CTP/Preview is blocking your object by querying pluginFallbackType: http://dxr.mozilla.org/mozilla-central/content/base/public/nsIObjectLoadingContent.idl.html#l38
Assignee: nobody → jschoenick
OS: Windows Vista → All
Hardware: x86 → All
Jorge, just wanted you to be aware of this one in case you wanted to mention it somewhere in "for developers" or in other extension-developer channels.
I tried with the playPlugin(): > obj.QueryInterface(Components.interfaces.nsIObjectLoadingContent).playPlugin() and it is working fine. Thank you for the help.
Summary: Using Java in extensions with Click-to-Play enabled → Plugins in chrome content should not be click-to-play
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.