After removing click-to-play in Chromium, Java applets aren't blocked when plugins are disabled in the content setting (http://crbug.com/50506). Turns out, this was already broken some time before click-to-play landed, namely since http://trac.webkit.org/changeset/60178. Even before that, applets were only blocked pretty much as a side effect of the code removed in that revision. Patch forthcoming.
Created attachment 62964 [details] Check if plugins are allowed before creating a Java applet
Bonus: with this patch, you also get the plugins blocked bubble (you didn't before).
Comment on attachment 62964 [details] Check if plugins are allowed before creating a Java applet This is not a Chromium-specific patch. Do all platforms want to block Java if plug-ins are blocked?
Comment on attachment 62964 [details] Check if plugins are allowed before creating a Java applet R+CQ=me No other ports override allowPlugins to block plugins on a per-frame basis. Other ports use the global settings to block Java, etc. It seems appropriate to me to treat Java as a plugin. (It is an ordinary NPAPI plugin these days, at least on Windows.)
Comment on attachment 62964 [details] Check if plugins are allowed before creating a Java applet Clearing flags on attachment: 62964 Committed r64311: <http://trac.webkit.org/changeset/64311>
All reviewed patches have been landed. Closing bug.