This was suggested by an add-on author, and I think it's a good idea, given that we almost always reject add-ons that include NPAPI plugins. What to look for: The add-on has a "plugins" directory in the root of the package, with at least one DLL file in it. Only extensions can have this. What to do: Show a warning with the following message: NPAPI plugins are generally not allowed in extensions. The only approved channel for plugins is the Plugin Finder Service.
Should I show an error if there is a plugins directory with DLLs and the add-on is *not* an extension?
It's not necessary. A DLL in a non-extension should be enough to raise several flags with editors.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Should this be up on preview already? This page doesn't show the new warning: https://addons.allizom.org/en-US/developers/addon/bitdefender-quickscan/file/103054/validation
Kumar hasn't said anything and this is one of the most recent things that I've pushed, so it probably isn't.
Whoops, just saw this. Pushed to Zamboni in https://github.com/jbalogh/zamboni-lib/commit/2affece
verified fixed @ https://addons-next.allizom.org/en-US/developers/upload/8a017613e2d24a85a3711ae9400f6f09
Status: RESOLVED → VERIFIED
Bumping to .10, this didn't have any bake time so it missed .9.
Target Milestone: 5.12.9 → 5.12.10
Reclassifying editor bugs and changing to a new whiteboard flag. Spam, spam, spam, spam...
Whiteboard: [required amo-editors] → [ReviewTeam]
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.