browser_specific_settings

[maxik34]

I've been working on an extension, and the error Unrecognized manifest key 'browser_specific_settings' that appears after every reload of the extension is annoying. Yes, this is not an error, but only a warning. But the user who will use the extension will see the Errors button. It will feel like the extension is broken.

I'm not suggesting implementing this key and adding some functionality to it, I'm suggesting just ignoring it so that this message does not appear anymore.

It's ridiculous to make two identical versions of an extension, the difference being that one manifest file will have this parameter (for working in Firefox), and the other will not.

[Half-Modern]

Upstream Chromium issue.

[win32ss]

Yes, Chrome has never supported this key. So even Supermium were to ignore this dependency it wouldn't help anyone running this extension in other Chromium browsers.

[maxik34]

Yes, but let it be fixed at least here.
When I was working with the source code of Source SDK 2013, I found a small typo that slightly broke the functionality of one entity and it turned out that this typo had not been fixed in any of the Source games, so I decided to propose fixing this typo for P2CE and Mapbase, so that at least it was fixed there.
Google will most likely never fix this, but we can, even if only for this chromium project.