On Jul 22, 2011, at 12:19 PM, danchik wrote: > There might be another issue now, I think safari 5.1 (even when ran in 32bit) > now loads the plugins in another process through > com.apple.WebKit.PluginProcess instead of loading them in the same process as > Safari as it used to before the 5.1 :( In which case nothing wont help since > the plugin in question expects to operate in the same process as the Safari.
Yup. This is pretty important for security and stability reasons. (Chrome has always done this.) You’ll need to live with the fact that you’re not in the same process anymore, and fix whatever incompatibility you have. —Jens_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
