3 ms·
Firefox went through this before with the migration to WebExtensions in 2015. (That's when I stopped maintaining an extension that I no longer cared about.) I g
by skybrian 4y ago
Firefox went through this before with the migration to WebExtensions in 2015. (That's when I stopped maintaining an extension that I no longer cared about.) I guess it's Chrome's turn now?
I expect, though, that users won't mind as much? I run very few extensions these days, due to the security risk, not wanting to vet extension authors, and not wanting to pay attention to the security implications of updates due to things like author changes.