I can’t seem to find a clear answer on this anywhere.
How far back is it backwards compatible? Do I have to be concerned about creating multiple versions of the extension?
Thanks
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I can’t seem to find a clear answer on this anywhere.
How far back is it backwards compatible? Do I have to be concerned about creating multiple versions of the extension?
Thanks
"manifest_version": 2itself does not cause any incompatibility issues.But you can easily make a mistake and create an extension which is backwards-incompatible, by using features/APIs which are introduced in Chrome 18 or later (manifest v2 came with Chrome 18).
I suggest to not worry about the old manifest version any more, because only Chrome 17- is affected. As of writing, the current stable version is 23. Hardly anyone is using Chrome 17 any more.
See also