Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Firefox 76 back button does not return to exit location (ie returns to top of page) in SAFE MODE

more options

Ever since the upgrade to Firefox 76.0 on Windows 10 Pro ... sometimes I click on a link ... then click on the back button ... I am returned to the top of the page instead of the location from which I exited the original page

I have seen this reported several times ... with the workaround of Open Link in New Tab (which I have had to use for YouTube for several years) ... but now all pages (including my own) ... exhibit this problem

I have started Firefox in safe mode as well as with all plugins disabled ... and the results are the same

The page in question is my BOOKMARKS.html from this or any other profile ... if that helps

Ever since the upgrade to Firefox 76.0 on Windows 10 Pro ... sometimes I click on a link ... then click on the back button ... I am returned to the top of the page instead of the location from which I exited the original page I have seen this reported several times ... with the workaround of Open Link in New Tab (which I have had to use for YouTube for several years) ... but now all pages (including my own) ... exhibit this problem I have started Firefox in safe mode as well as with all plugins disabled ... and the results are the same The page in question is my BOOKMARKS.html from this or any other profile ... if that helps

Solution choisie

Firefox 77 seems to have resolved this issue ... for now

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (2)

more options

Solution choisie

Firefox 77 seems to have resolved this issue ... for now

more options

Hi dicecollector, if you were opening your bookmarks page from disk -- in other words, it had a file:// address -- then yes, this was a problem in Firefox 76 that was fixed in Firefox 77.

Ref. https://support.mozilla.org/questions/1286157