Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

FF ESR 78.7.1 (32-bit) vs. FF 85.0.2 (64-bit) rejected by a site I need to use

  • 3 svar
  • 1 har dette problem
  • 1 visning
  • Seneste svar af wgk

wgk
wgk
more options

The ESR release is apparently behind an update, likely security oriented (the site ESR is rejected by is a Bank). I've been told by the site that they test (essentially) Chrome...and go with THEIR updates, if it suits their purposes. They suggested blowing away the ESR history (...cookies and all of it) and restarting ESR. Afteer that didn't work, I'm presuming the fix the Bank wants is in FF 85.0.2 and not in 78.7.1 ESR. But, I'm guessing.

I realize ESR stages ESR releases to follow FF so to allow testing ahead of FF auto update migrations. It's one reason why I use ESR most of the time. But, I think it would help if we could have some way to associate ESR's release cycles (Versions) to FF (Versions) with dates and expected. Maybe it is somewhere.

Q. What is the relationship, if any, between the versions FF vs ESR? Is ESR 78.7.1 = FF 78.7.1 or what? Q. If not, what? Where/What is the relationship and is the timing set or variable on progressions of ESR?

Thx wgk

The ESR release is apparently behind an update, likely security oriented (the site ESR is rejected by is a Bank). I've been told by the site that they test (essentially) Chrome...and go with THEIR updates, if it suits their purposes. They suggested blowing away the ESR history (...cookies and all of it) and restarting ESR. Afteer that didn't work, I'm presuming the fix the Bank wants is in FF 85.0.2 and not in 78.7.1 ESR. But, I'm guessing. I realize ESR stages ESR releases to follow FF so to allow testing ahead of FF auto update migrations. It's one reason why I use ESR most of the time. But, I think it would help if we could have some way to associate ESR's release cycles (Versions) to FF (Versions) with dates and expected. Maybe it is somewhere. Q. What is the relationship, if any, between the versions FF vs ESR? Is ESR 78.7.1 = FF 78.7.1 or what? Q. If not, what? Where/What is the relationship and is the timing set or variable on progressions of ESR? Thx wgk

Valgt løsning

Two very helpful responses. Thank you both. Wouldn't you know. Both FF and ESR work today. My suspicion is that my machine's going through a sleep/hibernate cycle last night might have finished off the History Clear I did not ESR yesterday that didn't work. I should have tried a machine restart rather than just an ESR restart, maybe. Thank you for the really thoughtful and interesting solutions and the quick comebacks. It is sleep depriving to think your Bank access is boffed because IT wants you to use Chrome and you are pretty sure you know better......mark this one SOLVED. wgk

Læs dette svar i sammenhæng 👍 0

Alle svar (3)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

The Extended Support Release is built using one new base version of Firefox every year. Starting this Summer, the next ESR will be based on Firefox 91.

Do you think your bank would be fooled if your Firefox identifies itself as Firefox 85? If you want to try that, here's how you can make that as a global change; I don't know whether there is a way to make the change only for one site.

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

(2) In the search box in the page, type or paste the new preference name

general.useragent.override

(3) On the bar with the bolded preference name, click the radio button next to String and click the + button to add the preference. Then Firefox should display a blank field for editing.

If you don't see Boolean Number String and a + button, this preference might already have been created. Double-click the current value to enable editing.

(4) Paste the 64-bit Firefox 85 user agent string --

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0

-- and click the blue checkmark button to save the change.

(Screenshot illustrating is attached.)

This should take effect in newly opened or reloaded pages.

If other sites stop working normally, you might need to delete the preference. It's hard to keep track of what has changed in the past 7 versions that sites might care about.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Do you see any serious error messages in the Web Console when you visit this website or are some features not working ?

Usually websites that have a warning about older browsers have a button to proceed or have a note that some features aren't working. Also blocking cookies or using content blocking extensions can have more impact in case like this. It is always better to test for support of features instead of blocking browsers.

wgk
wgk Spørgsmålsstiller
more options

Valgt løsning

Two very helpful responses. Thank you both. Wouldn't you know. Both FF and ESR work today. My suspicion is that my machine's going through a sleep/hibernate cycle last night might have finished off the History Clear I did not ESR yesterday that didn't work. I should have tried a machine restart rather than just an ESR restart, maybe. Thank you for the really thoughtful and interesting solutions and the quick comebacks. It is sleep depriving to think your Bank access is boffed because IT wants you to use Chrome and you are pretty sure you know better......mark this one SOLVED. wgk