Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Sudden jump back to top in Google+

  • 3 odpovědi
  • 2 mají tento problém
  • 4 zobrazení
  • Poslední odpověď od DavidGreen

more options

When scrolling down through Google+ news feed, without any noticeable change or prompting, the viewing area is jumped back to the top of the news feed, where you have to scroll back down to the point where you were reading. Aside from disrupting reading, there is no other effect.

This issue does not present itself on Chrome or IE.

When scrolling down through Google+ news feed, without any noticeable change or prompting, the viewing area is jumped back to the top of the news feed, where you have to scroll back down to the point where you were reading. Aside from disrupting reading, there is no other effect. This issue does not present itself on Chrome or IE.

Zvolené řešení

David Green, Thank you for your question, however we were unable to reproduce this in Firefox. Please update to the latest version of Firefox and if this does not help, please consider a new thread to grab the attention one more time.

Přečíst dotaz v kontextu 👍 0

Všechny odpovědi (3)

more options

Zvolené řešení

David Green, Thank you for your question, however we were unable to reproduce this in Firefox. Please update to the latest version of Firefox and if this does not help, please consider a new thread to grab the attention one more time.

more options

Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

Thanks cor-el, I didn't know that the profile could be managed. The new profile appears to have corrected the problem. And to be safe, I have elected to rebuild rather than copy the profile contents.