Privacy/Reviews/Telemetry/Encountered Plugin Types: Difference between revisions

Privacy/Reviews/Telemetry/Encountered Plugin Types (view source)

575 bytes added , 13 August 2011

no edit summary

35

edits

@@ Line 36: / Line 36: @@
 # Understanding which plug-ins and which versions of those plug-ins are in use and how frequently they run (including trends) will help us determine when it's reasonable to ship a 64-bit build of Firefox (which requires special and only somewhat available 64-bit plug-ins).  Essentially, when almost all object types encountered can be run by available 64-bit plug-ins, we can ship something that no longer supports 32-bit plug-ins.
+## A 64-bit Firefox will have to run 32-bit plugins as well as the currently-rare 64-bit plugins. Plugins don't ship in 64-bits because browsers can't run them, so what we've done on Mac & Linux and will have to do on Windows is run a 32-bit plugin in a separate 32-bit process from the 64-bit browser. It's really just a difficult engineering problem ({{bug|595053}}). And the data collected here would be from 32-bit Firefox users who can only use 32-bit plugins on Windows, so it would only say that zero 64-bit plugins are used in 32-bit browsers, which we already know.
 # Understanding the commonly encountered object-types, we can identify the "most likely needed" plug-ins to feature in our plug-in finder.
 # Understanding the extent of a problematic plug-in's reach can help us estimate what effect blacklisting it may have.