I should note that the persistence of scroll position is applied across every job configuration page. In effect if you scroll to "Post-build Actions" on JobA and then navigate to the configuration of JobB, the page will scroll incorrectly

This made sense when it was real tabs (Jenkins remembers where you were!), but needs to be removed now.

Gus is planning to remove this PR-2117

I kind of like the tab memory, even in the scroll situation. The fact that the tabs didn't show up is a real bug, though. I am submitting a fix.

gusreiber The problem is that memory does not seem to behave in any way predictable. With shorter sections, you can never really know which section you're in. And the scrolling in the case of a short config form is also weird, as it doesn't even reach your previous section (too many sections on the screen). I mean, I knew of this feature in tabs, it was obvious it's still in there in scrolling, but I had no idea WTF it's doing. Imagine not knowing about it.

I thought I had fixed this, but will double check to see if it has been re-introduced.

gusreiber Haven't seen this is a while, so if the scroll is gone, that would be great and you can just resolve this.

danielbeck In checking this guy out I was able to catch the tab bar not pegged at the top of the screen doing the sort of back-n-forth testing you are describing. The issue is a similar root cause, scroll position faked out by browser's own state memory. So I have offered this PR: https://github.com/jenkinsci/jenkins/pull/2219

closing the issue, since Daniel isn't seeing it. I think I only saw a similar issue because Chrome was tripping over the debugger. Will check again when we open back up for 2.1