On Fri, Aug 28, 2009 at 11:03 AM, John Abd-El-Malek<[email protected]> wrote: > Can't we blacklist nspluginwrapper, and use the same logic that it uses to > find the real plugins?
I have been thinking about this. The tricky part is that for *some* plugins, nspluginwrapper is the best we currently can do, because it's used to bridge 64-bit browsers to 32-bit plugins. But I think if we scan all plugins, we can pick and choose between them and we should prioritize native plugins over nspluginwrapper'd ones when they are available. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
