Linked by Thom Holwerda on Thu 10th Jun 2010 22:59 UTC
Permalink for comment 429900
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-23
Maybe this are two solutions:
"The reason for this is that NSPluginWrapper 'wraps' 32bit plugins in such a way that other 64bit browsers can use 32bit plugins. It does this by creating a 64bit executable named 'npwrapper.originalpluginname' for each 32bit plugin and this in term runs the real 32bit executable. This works very nicely for Firefox, which cannot handle plugins of a different architecture itself.
Opera however, doesn't need NSPluginWrapper and indeed all it does is serve to cause our own wrapper (which performs the same purpose) to get confused, since we detect the architecture of the NSPluginWrapper (64bit) instead of the actual plugin (32bit). What we need to do is ignore all NSPluginWrapper wrapped plugins by default and indeed there is a bug filed suggesting we do exactly that. In the mean time we do have a system for setting certain plugins to be ignored."