uBlock Origin still works in Chrome 139

3 pointsAuthorizedCust7mo ago2 comments

In various places, it was alleged that uBlock Origin will no longer work in Chrome 139 as that is when Manifest v2 will be removed.

I just upgraded to 139.0.7258.67, and uBlock Origin 1.65.0 is working as always.

With 138, I reconfigured Chrome to force Manifest v2 to continue working. But even Google's guidance (https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline) suggests that for 138, Manifest V2 is "disabled" and "Users can no longer turn them back on." For 139, for enterprise users, "the ExtensionManifestV2Availability policy will be removed", further clarified with "Manifest V2 extensions will cease to function for any user upgrading to Chrome 139".

Did something change?

2 comments

qilo7mo ago

It's not working for me anymore, after upgrade to 139.

chrome://policy/ shows policy status error:

  Policy name                        Policy value    Source      Applies to    Level        Status

  ExtensionManifestV2Availability    2               Platform    Machine       Mandatory    Error
                            Value    2
                            Error    Unknown policy.

Update: Add these options to the chrome executable to make it work again:

  --enable-features=AllowLegacyMV2Extensions,UnexpireFlagsM136,UnexpireFlagsM137 --disable-features=ExtensionManifestV2Unsupported

Actually, these are enough:

  --enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2Unsupported

qilo7mo ago

With 138, I reconfigured Chrome to force Manifest v2 to continue working.

How did you forced?

j / k navigate · click thread line to collapse

uBlock Origin still works in Chrome 139

3 pointsAuthorizedCust7mo ago2 comments

In various places, it was alleged that uBlock Origin will no longer work in Chrome 139 as that is when Manifest v2 will be removed.

I just upgraded to 139.0.7258.67, and uBlock Origin 1.65.0 is working as always.

Did something change?

2 comments

qilo7mo ago

It's not working for me anymore, after upgrade to 139.

chrome://policy/ shows policy status error:

  Policy name                        Policy value    Source      Applies to    Level        Status

  ExtensionManifestV2Availability    2               Platform    Machine       Mandatory    Error
                            Value    2
                            Error    Unknown policy.

Update: Add these options to the chrome executable to make it work again:

  --enable-features=AllowLegacyMV2Extensions,UnexpireFlagsM136,UnexpireFlagsM137 --disable-features=ExtensionManifestV2Unsupported

Actually, these are enough:

  --enable-features=AllowLegacyMV2Extensions --disable-features=ExtensionManifestV2Unsupported

qilo7mo ago

With 138, I reconfigured Chrome to force Manifest v2 to continue working.

How did you forced?

j / k navigate · click thread line to collapse