hi

hi Harzilein

is this correct ?

"SeaMonkey 2.53.2 uses the same backend as Firefox and contains the relevant Firefox 60.3 security fixes."

Should it say, as Firefox 56 ?

therube: for which part? the same backend as Firefox 56? or contains the relevant Firefox 56 security fixes?

60.3 is correct. It has all security fixes up to 60.3 and a lot more. Just not 100%. The worst ones are all in up to current Fx.

perhaps both should be mentioned?

njsg basically it is not 56 and not 60 also. We could probably write originally based on 56 but no one would be the wiser then. Code in relavant parts ist constantly being upgraded now.

njsg maybe just drop "uses the same backend as Firefox".

frg_away: For the average user (me) .... what is "backend" verses "the rest"??

I'll get that answer tomorrow!! ;-)

Maniel what was once Gecko unless you want to call the current stripped down and mutiliated engine it.

It's no longer called Gecko?

Lightkey: not sure what they call it in the current version of Firefox

Lightkey it is called Gecko but is it Gecko ?

AFAIU only parts of Servo were included in Gecko so far, so it is Gecko.

Lightkey It is not was added it is what was removed.

It is still called Gecko

and FWIW, the XUL stuff was only a hacked-on workaround because HTML was too stupid to do UI back in the 90s, Gecko has in fact been extended and improved, not stripped down. But whatever. Haters gonna be haters.

KaiRo_Mozilla I am no hater just completely indifferent when it comes to current Gecko now. Market share of current Firefox seems to agree with me. Going down all the time. And every time someone critizes Mozilla they will just clam up and put the one in a "hater" corner. No room anymore for self criticism. Just bunker mentality. We are the good ones all other are bad and want to do bad...

...things to us.

frg_away: is it still possible to say features from Firefox version XY are present, or that doesn't make sense anymore?

IMHO it would be useful to have a version number to check if some feature is available or not (say, in tables like developer.mozilla.org/en-US/docs/We…_Observer_API#Browser_compatibility )

njsg It is unfortunately all over the place. If you have bug numbers you can always check against Bills patch queues. Everything for 56 is of course in. Not ideal but the best we can do with small resources. Basically cherry picking as much as possible.

njsg: firefox featres from version 56 are indcluded secuity patches from firegox 60.3 are included and major security issues post fx 60.3 are inluded. does that answer your questions? but then we also included media changes to use the rust mp4 parser under linux and not use libstagefright at all becuase of issues compile libstagefrght under clang 9 but that change will not bi in till 2.53.3

therube: good way to get people to shop at home depot instead of lowes. thx :-)

So (if that makes sense) "Seamonkey 2.53.2 uses the same backend as Firefox 56 and contains all relevant security fixes up to Firefox 60.3.", and possibly a list of features newer than Firefox 56?