2

Chrome's PPAPI version of Flash is now half the speed of the NPAPI version. This is purely unacceptable. In both using Stage3D and conventional Flash Display list, PPAPI lags miles behind in performance and doesn't even make use of hardware acceleration for Stage3D compared to NPAPI which makes full use of it.

My question is, I already know there's a way to detect if PPAPI is being used but, can the NPAPI version of Flash be forced upon Chrome users in any way perhaps via headers or Javascript?

My current solution is to simply show a small tutorial to manually disable Flash PPAPI whenever that version of the plugin is detected but it would be much more convenient if I could silently force the use of the NPAPI plugin in the background.

Is it possible?

xLite
  • 1,441
  • 3
  • 15
  • 28

1 Answers1

0

There's no way to do this. If you found one, it would be a security issue and would be fixed, because if an attacker could silently force-switch a user from the sandboxed PPAPI plugin to the unrestricted NPAPI plugin, then the whole security benefit of having a sandboxed plugin would be lost.

(And hopefully your tutorial is pointing out to users that following your instructions increases their vulnerability to attacks from malicious websites, so that they are making an informed decision.)

smorgan
  • 20,228
  • 3
  • 47
  • 55
  • Do you possibly then have any insight as to why it's so slow? Is the fact the plugin is sandboxed the reason it's so slow? – xLite Jun 12 '13 at 14:49
  • Filing a bug is the best way to figure out what the issue is, and get it addressed. – smorgan Jun 13 '13 at 04:10