I
discussed this bug last year in this forum and reported it at
https://crbug.com/1351379. A few days ago, "sheriffbot" reminded me that the issue has been available for over a year. I just re-test ed it with "extension-update-testing-tool", the bug still exists.
For more clarity, I rephrase the problem below.
1. You have a MV2 extension. The manifest is:
{
"name": "Bookmark Favicon Test",
"description": "Bookmark Favicon Test",
"version": "1.0.0",
"manifest_version": 2,
"permissions": ["chrome://favicon/", "bookmarks"],
"icons": {"128": "icon.png"}
}
2. You modify the manifest to MV3:
{
"name": "Bookmark Favicon Test",
"description": "Bookmark Favicon Test",
"version": "2.0.0",
"manifest_version": 3,
"permissions": ["favicon", "bookmarks"],
"icons": {"128": "icon.png"}
}
3. Now, the browser will disable the extension when upgrading it from MV2 to MV3.
From a developer's point of view, essentially the "favicon" and "chrome://favicon/" are the same permission and shows the same permission warning. The bug is that the browser does not treat them as the same permission when the extension is upgraded.
extension details page: after installing mv2
extension details page: after installing mv3
extension details page: after upgrading from mv2 to mv3