Proposal for plugins "opting out" of handling resources

Stuart Morgan stuartmorgan at
Wed Mar 14 13:25:17 PDT 2012

For the initialization check: encouraging plugin vendors to have their
plugin decide whether or not to load based on UA seems like an
anti-feature. Can you provide specific examples of reasons a plugin
written in what is intended to be a browser-neutral format would need
to use a browser whitelist or blacklist? A solution that's more
analogous to feature-detection would be much better if it's feasible.


Le 14 mars 2012 21:06, Rudi Sherry <rsherry at> a écrit :
> I just added a proposal wherein a new error code means the plugin would like to politely refuse to load, or handle a specific stream, and the browser would then use its default implementation as if the plugin didn't exist.
> The actual API changes are minimal: one new error code for some existing NP/NPP routines.
> Questions?  Comments?
> Thanks,
> Rudi
> _______________________________________________
> plugin-futures mailing list
> plugin-futures at

More information about the plugin-futures mailing list