If you disable NPAPI for B2G with a fatal configure warning, I think I could live with that. In the alternative, we could disallow instantiating plugins in a (packaged) app context.
Plugins delenda est. Andreas On Jul 23, 2012, at 9:36 PM, Jason Duell wrote: > Do we have any way within our NPAPI functions to determine what docshell the > plugin is displaying content in? I don't see an obvious one. > > For both per-tab private browsing (bug 722850) and B2G application "cookie > jars" (bug 756648) we need to implement separate simultaneous cookie > databases, i.e. have separate cookie namespaces. For most requests we can > get the AppId and/or private browsing mode from the necko channel's callbacks > (which now implement nsILoadContext on both parent/child in e10s). But the > cookie API allows callers to skip passing in a channel to > get/setCookieString, and that's what NPAPI does > > http://mxr.mozilla.org/mozilla-central/source/dom/plugins/base/nsNPAPIPlugin.cpp#2736 > > So I'm wondering how I can get the info some other way. > > thanks, > > Jason > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
