Extensions manifest should recognize “applications” key
Reported by
jtoj...@gmail.com,
Jan 2 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Steps to reproduce the problem: Install the extension What is the expected behavior? No errors will be printed. The “applications” key should be ignored. What went wrong? “Unrecognized manifest key 'applications'.” is printed in the extension manager. Did this work before? No Does this work in other browsers? Yes Chrome version: 55.0.2883.87 (Developer Build) (64-bit) Channel: n/a OS Version: Flash Version: “applications” key is a way to specify browser-specific properties. As such, it should be ignored by browsers that the message is not intended for. https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/applications
,
Jan 6 2017
Tested this issue on Ubuntu 14.04 using chrome latest stable M55-55.0.2883.87 by following steps mentioned in the original comment. Observed different error message saying "There were warnings when trying to install this extension: Unrecognized manifest key 'applications' as shown in the below screen-shot after installing the extension. jtojnar@ Could you please confirm is this is the issue you are talking about?
,
Jan 6 2017
Yes, this is the same issue. The difference in layout is probably caused by me using Chromium instead of Chrome. I had to click the Errors link before seeing the error.
,
Jan 8 2017
I am using Chrome 55.0.2883.87 (Official Build) m (32-bit) on Windows 7 and I just see a warning, not an error. Do you want the warning not to be displayed, or are you having trouble running the extension due to this warning/error on Linux? In other words, is this just a UI feature as far as you are concerned, or does this actually prevent you from developing and running and extension?
,
Jan 8 2017
It is only a warning, the extension still works.
,
Jan 8 2017
,
Mar 3 2017
The "applications" key only seems to be supported by firefox. It's not supported by Chrome so showing a warning is valid. A good workaround might be to generate different manifests for extensions on firefox and chrome. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Jan 4 2017Labels: Needs-Triage-M55