Поиск в Поддержке

Избегайте мошенничеств со службой поддержки. Мы никогда не просим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Сообщить о нарушении».

Learn More

Why doesnt the back arrow use one click for previous page?

  • 6 ответов
  • 1 имеет эту проблему
  • 31 просмотр
  • Последний ответ от Wesley Branton

more options

After a search on findagrave.com i have a list of names to look at, so i click on one and look at it and decide to go back to the list of names but I click the back arrow and no change until I click it again. So I notice when I right-click the back arrow it shows that two instances of the same page was loaded hence I must click twice on the back arrow to get back to the list page. WHY? this doesn't happen in edge or chrome.

Все ответы (6)

more options

I don't have the same issue. Try Firefox Safe Mode to see if it's an issue with an extension or something along those lines.

I've seen a similar issue with Bing services. In their case, it has something to do with how the website handles user accounts. Bing checks your login information each time you visit a page and then reloads the page. This creates an extra history item. This was only really an issue the first time you searched unless you were logged in.

Are you logged in on this website?

more options

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

The problem does not exist on findagrave.com in safe mode. So, I deleted the firefox sync account and removed the only add-on, adblock plus, but the problem persist on findagrave.com.

more options

the problem persist after REFRESH.

more options

problem not solved.

more options

A similar issue is being investigated by the Firefox developers. See bug 1515073 for more information.