This is a significant UX issue, and has been for as long as I’ve been using Coda. Auto-scroll gets triggered by many more scenarios than those @Andrei_Kharlanov has identified here. They are difficult to document and reproduce.
The user will be totally focused (eyes and brain) on the content where they are working, take some trivial user action like a mouse click some place, and the window will jump to some random location. The UX on this particular issue is like walking through a mine field. It would be difficult to think of a more “irritating” UX scenario than that!
There is never a time in any app that I use when I want it to automatically scroll away from where I, the user, have consciously positioned the app/window/screen to display exactly what I want it to display. (There will always be edge cases, but what is being discussed in this thread is beyond that.)
Imho, the code should be audited for all instances of
window.scroll() or whichever method is causing this, and each instance should be vigorously tested for UX. My suspicion is that it could just be removed in most cases.