MDN needs to add a column for SeaMonkey in its browser compatibility list tables.
I still think MDN should add a column for SeaMonkey in its browser compatibility list tables, but I now know the workaround:
Since 2.53.1, the SeaMonkey release notes say it uses the same back-end as Mozilla Firefox 60.x.
So if the browser compatibility number in Firefox's column is 61 or greater, then there's no support in SeaMonkey.
@arielmt That's... wild. I think stuff I've built, trying to minimize external libs and clever solutions assumes the existence of things in FF 80, because "Well FF 80 is ancient, surely that's safe"
Hmm.
@arielmt Yeah Seamonkey does not support ES2018 which is... I don't think you can expect much will work at all on it. My stuff uses extended RegExp and Promise.finally() I know, which Seamonkey won't support...
My response to this, as a meterstick: I'm adding "I don't support Seamonkey, get FF ESR" to my docs. x.x;
@arielmt also a useful metric for https://caniuse.com