and this is probably the most probably reason why you continuously re-open the config page, you have to always scroll down, or click the tab.
We went through a few iterations on this. Earlier alpha releases didn't scroll, but actually split job configurations into tabs, i.e. you were only seeing a single section at a time. One of the behaviors implemented there was that your browser remembered which tab it was on last (per job type I think), and automatically selected that one. I.e. repeated config cycles as you describe had you start on the script section, and only see that one, unless you selected something else.
Consensus later was that 'scroll tabs' are better, and with them, the automatic selection was extremely weird. I knew about this feature and still had no idea what was going on – the problem was, with everything on a single page, some sections may be so short that it's impossible to scroll down to them, etc.
So implementing anything resembling what you're requesting would probably require switching from "scroll tabs" to actual tabs.
michaelhuettermann I think you misunderstand "pipeline-view-plugin" component. it's for https://github.com/jenkinsci/pipeline-view-plugin , and you're talking about the UI of pipeline editor or whatever it is