3 ms·
a. It seems you're conflating the deprecation of XUL/legacy extensions and the NPAPI plugins here. This current release removes NPAPI support which affects plug
by Etzos 10y ago
a. It seems you're conflating the deprecation of XUL/legacy extensions and the NPAPI plugins here. This current release removes NPAPI support which affects plugins only. Extension changes are coming in later releases.
b. If they're acting in good faith why did they misrepresent when Mozilla announced they would be deprecating the NPAPI plugin API[1]? It seems more likely that they were simply lazy and instead of making the solution they used for Chrome (which already removed NPAPI support, mind you) work across the board, they waited until the last moment and realized Mozilla was actually going to go through with making the same changes they did.
[1] https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plu... which is a full year before Google mentioned Mozilla made the announcement ( https://www.fxsitecompat.com/en-CA/docs/2016/plug-in-support-has-been-dropped-other-than-flash/ https://www.fxsitecompat.com/en-CA/docs/2016/plug-in-support... )
- cpeterso 10y agoHangouts switched from NPAPI to WebRTC in Chrome back in 2014, but continues to use plugins (NPAPI or ActiveX) in other browsers. Hangouts depends on some non-standard WebRTC functionality in Chrome. https://plus.google.com/103171586947853434456/posts/39TCW3PcLye https://plus.google.com/103171586947853434456/posts/39TCW3Pc...
- threepipeproblm 10y agoYes, I think I am conflating the issues of XUL/legacy extensions and the NPAPI plugins. All I can say is that while I didn't take a lot of time to parse this, most of the people impacted by this issue will take even less. They will just understand that Firefox worked with Google Voice and then stopped. So it does seem to me like part of an overall theme. Firefox used to let users decide what was safe, now it's decided for us.