On 04/21/18 09:34 PM, Perry Wagle wrote:
The issue for me is the increasing use of what I think is bleeding edge
javascript to render just about everything. Today, I found that both
digitalocean and gmail won’t render on ESR52.
I'm still on 45ESR and Gmail works fine (besides some problems cycling
through the compose options, probably due to using a fork {OS/2})
But sure I can run another browser, but if I do on macOS, and set my default
browser to ESR52 (which it sees just fine), it works unless I either don’’t
have it open, or else have a newer Firefox already running, and then that
something starts up a profile manager window that doesn’t say which version of
Firefox is going to open that profile. And that means you can destroy your
ESR62 profile with the migration path to the hot new Firefox that you are
trying to port your life-saving legacy webextension to.
Mozilla seems to do zero testing for back-grading a browser instance and
officially don't support it.
Three solutions come to mind:
(1) Get the profile manager to at least say which browser is trying to open
that profile.
(2) Make ESR’s a real fork, and stop failing to pretend its FF52.
(3) Upgrade ESR52’s javascript engine to something more modern. (I assume that
this last is a non-starter, but I thought I’d ask after it).
(4) Sites not updating so fast as the ESR versions are _supported_
Generally I've found it takes a couple of years before a version really
starts to have problems.
Dave
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise
or send an email to [email protected] with a subject of
"unsubscribe"
