New
#31
Well except then of course the FF APIs will change over time and the plugins wont know about it and that is a recipe for crash/elevation exploits. Something a browser does NOT need. (BTW faking version numbers or "load anyway" hacks are doing just this. BAD security practice)
Plugins don't need to necessarily be tied to a browser version but they MUST be tied to an API version (Which is simplified to be the browser version)
Without version numbers either FFs programming API needs to be 100% fuuly backwards compatible for all time, or they need to dissallow plugins because doing neither is a giant computer crashy security risk.