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
sure crxviewer is extremely useful before installing a new addon (I'm using it on FF only).
But most of my usage stems from when I'm about to update any given addon. This is where crxviewer should shine most in my opinion. For any given addon/extension installed from AMO, and updated through are browser, being able to see the actual code change from previous version against the one we're being pushed an update from, would be an immense lever and overall responsible addons usage/"hygiene"..
There are many such online difftool available that accept zip file already..
I can't see of any better way to review the safety of any addon's update we're being pushed at. Doing so manually could be allevieated a lot with such a feature integrated to crxviewer.
The text was updated successfully, but these errors were encountered:
This would be a useful feature. As a reviewer on AMO, I already have access to a (simple) built-in diff tool. For anything more complicated I download the zip/xpi files and perform a local diff.
sure crxviewer is extremely useful before installing a new addon (I'm using it on FF only).
But most of my usage stems from when I'm about to update any given addon. This is where crxviewer should shine most in my opinion. For any given addon/extension installed from AMO, and updated through are browser, being able to see the actual code change from previous version against the one we're being pushed an update from, would be an immense lever and overall responsible addons usage/"hygiene"..
There are many such online difftool available that accept zip file already..
I can't see of any better way to review the safety of any addon's update we're being pushed at. Doing so manually could be allevieated a lot with such a feature integrated to crxviewer.
The text was updated successfully, but these errors were encountered: