Open alexsch01 opened 9 months ago
What is the expected result?
Chrome PDF Viewer is Manifest Version 2, among other extensions shipped with Chrome. See chrome://extension-internals
So is this
{
"manifest_version": 2,
"name": "Chrome Screen AI",
"version": "121.3"
}
in CfT Version 121.0.6167.0 (Official Build) (64-bit).
I don't see how Chrome is allegedly deprecating Manifest Version 2 for developers in the field yet shipping new internal extensions written using Manifest Version 2 without even describing what the code is doing in the extension manifest.
What is the expected result?
I would expect the browser to still launch ok, just with the MV2 extensions no where to be found
@guest271314 @mathiasbynens
As of Chrome (Windows 64-bit) 120.0.6099.63, these are installed by default with manifest_version
< 2
"manifest_version": 1,
"name": "Web Store",
"manifest_version": 2,
"name": "Chrome PDF Viewer",
"manifest_version": 2,
"name": "Google Network Speech",
"manifest_version": 2,
"name": "Google Hangouts",
"manifest_version": 2,
"name": "Chrome Web Store Payments",
It just seems wrong to me to announce a depreciation date for MV2 extensions and there are still 4 preinstalled extensions that are still on MV2
"manifest_version": 2, "name": "Google Network Speech",
Note, on Chrome, when Google voices are used for Web Speech API SpeechSynthesisUtterance()
a network request is mader that sends user text to external Google cloud servers. See https://github.com/guest271314/GoogleNetworkSpeechSynthesis.
On Chromium Google voices are not available. A local speech synthesis engine is used through SPeech Dispatcher. TTS/SST should be shipped in the browser. It's not right now.
Is there a way to simulate Chrome Manifest V2 deprecation?