This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When typing comments in Facebook using Chrome or Microsoft Edge, if I use the backspace key on my keyboard, the entire window jumps up a page so where I was typing is now just off the top of my screen and I have to scroll up to see what I'm typing and if I have to use my backspace again, it scrolls off the top, again.
Is anyone else's Facebook page jumping like this? It only happens on Facebook too by the way.
Original Title: Is anyone else's Facebook page jumping like this?
Troubleshooting website display or functionality issues in Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Go into your setting and adjust zoom until it stops. It could be 75% to 90%. seems to be the only solution I have found to work.
The same has been happening to me and I'm using Windows 10 and Chrome browser.
This is a total pain, I used google chrome browser and since Adobe deleted the Flash I find I can't play some games on my laptop , Plus this jumping up when I hit backspace ....stops you enjoying being on the internet--- read a couple of answers above and went in and changed the zoom on my page to 100 and now its stopped jumping
How to fix the Facebook auto scrolling bug in Windows 11, regardless of browser being used [it was happening for me on Chrome].
You're welcome.
Hello, Carol, just update your office.
I've had the same problem, and I'm not using Microsoft Office (not at all). As a programmer myself, the problem apparently is not in Facebook, or Chrome, but is a glitch (probably in one of the Windows routines that are getting used) that show up in the specific situation that is getting set up. Might have to do with a screen pixel position, or a bad memory pointer, an overflow situation, or something else. The fact that it's (obviously) so repeatable (in the specific situation that makes it show up), means that if "somebody" at the Microsoft team(s) responsible for the routines involved were to sit down with it, they could track it down and fix it. My guess is that it's buried in one or more of the routines that are formatting and redisplaying the text block that's being entered (and reformatted/redisplayed) as the keystrokes are being entered.