When I'm writing a topic, If I begin to go down enough the page constantly moves back to the top even if I scroll back down. Then it kind of jumps up and down while I'm typing like an earthquake on the page. This is really starting to upset me, in other words, piss me off. It's been happening for a very long time and I've been too lazy to say anything about it. I've even tried changing the skin of my SEN page. Not helping. Does anyone mind fixing this, or telling me how? I'd really like to write a topic without it being all messed up.

EDIT: And when I press enter, instead of dropping down a line, it makes a space in front of the current word. ...

That's actually weird. So you are writing several lines till a scrollbar appears and it randomly jumps up again?
I doubt it is SEN's fault. It's probably you pressing UP or whatsoever, you may check your key-locks which give keys a different meaning (notebooks got that very often).

Out of curiousity: someone else is having this problem?

Best answer I can give you is that its your own computer/keyboard rather than SEN. I've been on three laptops (My desktop is currently offline.) on SEN in the past 48 hours and have had no such issues.

My fingers are very far from the up arrow keys, or my keypad, so I know it's not that. Plus it's only letters I'm typing, with the spacebar and occasional enter that doesn't work.

Can't quite figure out what the bug is, but I have a few ideas. (Browser and OS would be helpful.)

JavaScript activation of any A whose href is "#" would scroll to the top.

When you fullview an image, SEN's JS essentially displays an (unpolished) modal at the very top of the page, and forcibly scrolls you there. If, for some reason, that particular function (inline_popup) is glitching, then it could have a constant scrolling effect.

This happens to me too. I hate it.

Try increasing the text form size when typing out posts or making topics (+ and - buttons in the top right of where you type your post).

I have this problem occasionally, but haven't had it on SEN, only other sites. Seems to be a random glitch of some sort, though I'm not sure what causes it.

Moose's statement indicates that this is a browser-related problem, but it would be difficult for anyone to investigate further (and perhaps find an outside fix) without knowing what browsers you guys use. (Don't even know if y'all're using the same browser -- and if you're not, then it's probably not a browser-related problem, meaning that there's something going on in SEN's code.)