GNOME Bugzilla – Bug 701161
Improve the extension update experience
Last modified: 2020-02-17 16:01:21 UTC
See patches. I don't like checking for updates at every login, but this is very similar to what browsers do, and should cause little network overhead.
Created attachment 245503 [details] [review] ExtensionDownloader: improve the experience with extension upgrades Show a notification after finding out that updates exists, and notify success or failure at the end of the operation.
Created attachment 245504 [details] [review] FileUtils: remove verbose log() We don't need to log each and every file we move.
Created attachment 245505 [details] [review] ExtensionDownloader: support the new format to check for updates The old format was submitting all the metadata, and that could easily reach the configured limits on the request size. But the site was using just the uuid and version, so pass that and nothing else.
Review of attachment 245504 [details] [review]: Uh, what's the unrelated extensionSystem.js changes?
Needless to say, given that we expose extension names, this goes best with bug 700966 (and now that I have a sweettooth installation, I can try build the server infrastructure for it)
Well, I would really appreciate if this could be updated and finally solved :) (I just needed to manually visit extensions.gnome.org and see that weather applet was failing due it being outdated :() Thanks a lot!
Looks like there are some extensions available for doing updates checking already: http://94.247.144.115/repo/Extension_Update_Notifier/