On Thursday, March 8, 2018 at 8:08:51 PM UTC+1, Thomas Elmiger wrote: > > Confirming: After the update a browser restart is necessary, otherwise the > ability to save is lost. (Mac, FF Developer Edition)
I don't think, it's a browser restart. IMO reloading the tab is enough. ... But I have to have a closer look, if we can detect, a plugin update, while the browser is running. .. > Maybe the plugin could spit out a warning? > I don't know, if that's possible. As I wrote, I'll have a look, if we can detect it. Every mechanism, that allows plugins to directly interact with the user can also be used to add-spam them. So the extension API is heavily restricted. We can't do what ever we want. > This is why I switched off auto-updates in the plugin settings some time > ago. Nevertheless I forgot to restart and had to export a JSON file from > the advanced search for the last changed tiddlers ... > The problem is, that testing plugin updates, can only done if you update the plugin. ... And the mechanism, how mozilla store updates happen is not always clear. The way I'd like, that updates are done is: - Give the developer the possibility to notify the user, that there is a new update - Then the user should decide, when the new addOn is installed. - Everyone would be happy. - BUT this notification mechanism can be used to spam users with adds .... So ?! -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ebe57b81-1a45-4e5d-acd4-63fc867bc9af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
