Confirmed users
699
edits
Plugins:PluginBugReporting: Difference between revisions
m
→Objections
m (→Objections) |
|||
| Line 222: | Line 222: | ||
* '''Concerns about user privacy''': have to trust plugin vendors not to send sensitive data in crash reports | * '''Concerns about user privacy''': have to trust plugin vendors not to send sensitive data in crash reports | ||
** '''Reply''': UAs already must trust NPAPI plugins to protect user privacy. This API extension exposes no more "private" information than is available to even well-behaved plugins. And UAs are expected to give users the option of sending the report, and what information known to the UA to send. | ** '''Reply''': UAs already must trust NPAPI plugins to protect user privacy. This API extension exposes no more "private" information than is available to even well-behaved plugins. And UAs are expected to give users the option of sending the report, and if so, what information known to the UA to send. | ||
* '''Some UAs already have crash databases, plugin vendors should use those instead''' | * '''Some UAs already have crash databases, plugin vendors should use those instead''' | ||
** '''Reply''': Plugin vendors need to reply to this point, see below. The idea is to offload from UAs some of the crash analysis burden, while additionally allowing plugin vendors to | ** '''Reply''': Plugin vendors need to reply to this point, see below. The idea is to offload from UAs some of the crash analysis burden, while additionally allowing plugin vendors to record information relevant to them (complementing what a UA finds relevant). | ||
* '''Google Chrome found that "a lot of" (?) OOPP crashes were UA bugs, not plugin bugs''' | * '''Google Chrome found that "a lot of" (?) OOPP crashes were UA bugs, not plugin bugs''' | ||
** '''Reply''': UAs need to approximately quantify "a lot" for themselves. (any Google Chrome data) | ** '''Reply''': UAs need to approximately quantify "a lot" for themselves. (any Google Chrome data available?) If the UA can't reliably determine when a plugin is indeed at fault, it probably shouldn't send plugin crash reports. | ||
* ''' | * '''Potential for bad user experience because of a non-uniform crash report UI''' | ||
** Any responses from people with UI experience? | ** Any responses from people with UI experience? | ||
* '''Risky API''': even if implemented by plugin vendors and UAs, may not improve plugin quality | * '''Risky API''': even if implemented by plugin vendors and UAs, may not improve plugin quality | ||