magicbus wrote:
DiskDoctr wrote:
Everybody running ESR?
You should be.
Firefox ESR
Hmmm.. doesn't seem like I fit the profile:
Who is it for?
Firefox ESR is intended for groups who deploy and maintain the desktop environment in large organizations such as universities and other schools, county or city governments and businesses.
Who is it not for?
Individual users who always want the latest features, performance enhancements and technologies in their browser without waiting for them to become available in ESR several development cycles later.
Dave
Anyone who wants to continue using normal browser functions meets the profile.
The odd wording has the goal of coaxing a large number of people into using the now-hobbled versions of browsers, which may not function properly on a number of sites.
This strategy, IMHO, is simply to force websites and companies to implement workarounds and changes to support the 'new way.'
The end users' reward for being 'part of the team' and moving forward? Broken sites, most without any notice of why it doesn't work, and limited functionality.
My suggestion is to stick with a fully functional model and let 'the rest of them' work it out first.
Stress levels and frustrations are usually much lower this way ;)
One example that is likely some people find: Comcast email (via OWA) has troubles with the way it calls the dialog box for attaching files to an email. So you can't do it with the 'new and improved' browsers (FF and Edge both).
There is a way to manually call the function, attach files, then back feed into a message to send an email, but that isn't something the average person would enjoy doing ;) I only did it to confirm the OWA server was functioning properly and nothing on the customers' side was blocking or interfering with it.
Bottom line? ESR = no hassles for you. Wait until it is fixed before switching.
Make sense? ;)
Edit to add: A little info about it, in case anyone is interested in more details
NPAPI support ending
