gerout.blogg.se

If your extension requires an account or special network environment, make sure that requirement is communicated to the user.It should be as obvious as possible for new users to understand how your extension works and verify it's behaving correctly.Make sure that your extensions clearly communicate error conditions to the user.Some file systems will treat these as the same file while others will treat them as two distinct files, causing Chrome to error when loading the extension. For example, say your background script was named Background.js, but your manifest.json references background.js. Ensure that all the files mentioned in your manifest.json are present in the package and their names and paths are correct.Verify that your submission contains the files you expect at the paths you expect.crx file onto the chrome://extensions page. Make sure that Chrome loads a packed version of your extension as expected by manually packing your extension and dragging the generated. Unpacked and packed extensions can have different behaviors.This may mean extracting resources from the package that you submitted. Test the exact files that you submit to the web store, not just a local development version of your extension.Test the code that you submit to the web store locally.Your item is just not functioning as it expected based on the item's listing.

A functionality in your item is not working due to a server side issue at the time of reviewing.The path or name of the files mentioned in your package are incorrect.This is most commonly seen with image files. There are files mentioned in your manifest that are not present in your package.Extensions should provide the functionality described in their listings and, if they cannot, communicate that to the user. The intent of this policy is to ensure a minimum quality level for all items published in the Chrome Web Store. # Functionality not workingĬorresponds to notification ID: Yellow Magnesium For example, Yellow Magnesium corresponds to the general class of errors where the extension does not behave as expected. These IDs are composed of two words: a color and an element. In order to make it easier to reference specific violations, the Chrome Web Store assigns each violation a human-readable ID. This page is provided to help you understand why your extension was rejected or removed from the Chrome Web Store and how you can fix the violation.Įach section in this document describes the issues that correspond to a particular category of violation.