In particular, potentially dangerous APIs may only be used in ways that are demonstrably safe, and code within add-ons that cannot be verified as behaving safely and correctly may need to be refactored. However, in order to maintain appropriate data security and effectively review code, we do have certain technical requirements that all add-ons must meet. In general, developers are free to maintain their add-ons in the manner they choose. Please read our Source Code Submission guidelines to avoid unexpected rejections or blocks. Minification of code with the intent to reduce file size is permitted. If external resources are used in combination with add-on code, the functionality of the code must not be obscured. Failure to provide this information will result in rejection or blocking.Īdd-ons are not allowed to contain obfuscated code, nor code that hides the purpose of the functionality involved. The code will only be used for the purpose of reviewing the add-on. The provided source code will be reviewed by an administrator and will not be redistributed in any way. Reviewers may ask you to refactor parts of the code if it is not reviewable. The author must provide this information to Mozilla during submission along with instructions on how to reproduce the build. Add-ons may contain transpiled, minified or otherwise machine-generated code, but Mozilla needs to review a copy of the source code before any of these steps have been applied. Source Code SubmissionĬode must be provided in a way that is reviewable. If corrections have been requested, the new version should not contain unrelated changes, as this complicates the review process and can lead to further rejections. To facilitate the functional testing, the add-on author must provide testing information and, if applicable, testing credentials required to use the add-on if an account is needed for any part of the add-on’s functionality. During review, the add-on undergoes basic functional testing in addition to code review. Add-ons with the sole purpose of promoting, installing, loading or launching another website, application or add-on are not permitted.Īdd-ons must function only as described.If the add-on is a fork of another add-on, the name must clearly distinguish it from the original and provide a significant difference in functionality and/or code.Such add-ons may be uploaded for self-distribution instead. Add-ons that are intended for internal or private use, are only accessible to a closed user group, or for distribution testing may not be listed on.Any add-ons, or add-on content, hosted on Mozilla site(s) must conform to the laws of the United States.Add-ons must disclose when payment is required to enable any functionality.All add-ons submitted for listing on are subject to Mozilla’s Conditions of Use.In addition, add-ons listed on must adhere to the following policies: If the add-on uses “Firefox” in its name, the naming standard the add-on is expected to follow is “ for Firefox”. The opt-in interface must clearly state the name of the add-on requesting the change.Īdd-ons that make use of Mozilla trademarks must comply with the Mozilla Trademark Policy.The permissions prompt shown when installing an add-on does not alleviate the need for an opt-in. Changes prompted by Firefox after the add-on is installed do not require an additional opt-in. The features must be “opt-in”, meaning the user has to take non-default action to enact the change.The add-on description must clearly state any changes made by these features.This includes features that impact user privacy or security, make unexpected changes to web content, change default settings like the new tab page, homepage, or search engine, or are not related to the add-on’s core function(s).Īny “unexpected” feature(s) must adhere to all of the following requirements: “Unexpected” features are those that are unrelated to the add-on’s primary function, and are not intuitive from the add-on name or description. Please consult our best practices guide for creating an appealing listing. The add-on should have an easy-to-read description about everything it does, and any information it collects. Users should be able to easily discern what the functionality of your add-on is and should not be presented with unexpected user experiences after installing it. Removing your extension from distribution.Will I ever be able to sell through AMO?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |