On Fri, 2017-10-13 at 14:26 +0000, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Oct 13, 2017 at 02:55:37PM +0100, Peter Oliver wrote: > > On Fri, 13 Oct 2017, Zbigniew Jędrzejewski-Szmek wrote: > > > > > All the energy devoted to this thread would imho be better spent on > > > trying to encourage the authors of popular extensions to update to the > > > new model, > > > > My understanding is that the new API lacks capabilities needed to > > make some extensions possible. Mozilla may or may not reimplement > > some of these functionalities in the future, but, for the time > > being, there’s little that the authors of such extensions can do. > > Sure, that's what everybody knows. But without going from generalities > to details of a specific extension, we're just speculating idly. Someone's given one example already, here's another: https://addons.mozilla.org/en-US/firefox/addon/calomel-ssl-validation/ "IMPORTANT: Development of the Calomel SSL Validation addon has been put on hold. Mozilla is disabling XUL and XPCOM in Firefox which means the addon is no longer able to query the current browser tab for the TLS certificate and cipher information." Sure, you can just manually inspect the details of any given site's certificate and TLS config, but Calomel's icon and grading system made it much easier to notice when some important site had a bad config. :/ -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
