Adblock plus new permissions update#

Then the metadata format and even the filename is changing occasionally. Then which revision should we compare against anyway? If you compare against the previous revision you might not see the warning if there is already a commit on top, if you compare against the last release tag, we would now spam every developer with a warning until we had the next release. We would need support for both hg and git.

There's no expectation of such a system covering all cases.Р вЂќР вЂЎirst of all how would you even identify a change? The only way to do so at build time (and later would be pointless) would be by comparing the current metadata against some previous revision, and this is just a mess. We could, for instance, have warnings when certain parts of the manifest, which might cause a permission warning, change and we could even prevent changes that we have identified to reliably cause such a permission warning.

Adblock plus new permissions update#

On the other hand what risk do we face, if we just test it with our devbuild? When the extension gets disabled on update due to permission changes, I will just backout the change, and in the worst case we just lose some devbuild users which got the update before I undid the change. And in the end that dummy extension will remain forever in the dashboard of whatever account was used for this test. I don't have access to our Chrome Web Store account, so only Felix or Wladimir could do that, or somebody has to do it with their private developer account (if you don't have one yet, getting one is quite a process, involving paperwork and a payment of 10 USD). That would be a pain to do - and I don't volunteer - but perhaps it's worth it given the risk?