You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
In my discussions with Chromium, there are two layers of possible fixes:
We wait for them to push a security fix to Chromium core
We apply a fix that the Chromium team gives us, which will require a new release to be made
Option 2 is generally preferable, since it will be quicker, but Chromium has not yet provided us this fix, and it may or may not actually work. It's not clear to me that it will work, since I don't have an abundance of knowledge about how the particulars of Extension Content Verification work.
I'm not completely against releasing a new version before they push a fix if necessary, but all other things being equal I'd rather not if it is not necessary.
Activity
Hainish commentedon Sep 12, 2016
This is blocking on updates from Google.
jeremyn commentedon Sep 12, 2016
Are we waiting for Google to fix their "reactivate extension" logic before we push a new version and, hopefully, reactivate everyone's extension?
J0WI commentedon Sep 12, 2016
Is the ruleset base already freezed or will current commits still hit the 5.2.5 release?
Hainish commentedon Sep 12, 2016
@J0WI new commits will make it in.
In my discussions with Chromium, there are two layers of possible fixes:
Option 2 is generally preferable, since it will be quicker, but Chromium has not yet provided us this fix, and it may or may not actually work. It's not clear to me that it will work, since I don't have an abundance of knowledge about how the particulars of Extension Content Verification work.
I'm not completely against releasing a new version before they push a fix if necessary, but all other things being equal I'd rather not if it is not necessary.
Hainish commentedon Sep 19, 2016
This will be deployed this week. Chromium has failed to give us a way forward with option 2.
J0WI commentedon Sep 20, 2016
#6920 might be also worth having a look at.
Hainish commentedon Sep 22, 2016
This has been deployed