The issue has been closed
Title.
Is there a reason why this couldn't or shouldn't work in Firefox v78?


posted by busches over 3 years ago 
Supporting older releases would likely mean having to set up postcss and Babel to ensure that they are not continuously broken since none of us uses them.
However they probably still wouldn’t work because often older version contain webextension-related bugs that we just don’t expect while writing anymore.
My suggestion, however not easy, would be to keep a fork that includes these adjustments and then deal with the breakage that might happen over time.
posted by fregante over 3 years ago
For reference, here's the Firefox release schedule: https://wiki.mozilla.org/Release_Management/Calendar
I just realized that postcss/babel can't fix the changes brought in #4361. Supporting ESR would mean we have to keep its compatibility in mind instead of just testing on the last version of browsers.
Officially we won't test/support ESR, but if any developer uses ESR, they can open PRs and take care of that compatibility themselves, as long as they're small changes and they're doing the testing themselves. I'm going to close this for this reason, but PRs welcome.
posted by fregante over 3 years ago