Any chance to get auto scrolling disabled? It is making blueocean very hard to use.

Every time there is an output update from a build step the page is auto scrolled down. I understand this can be perhaps useful the first (once) time but not every time.

When you have parallel builds. Click on one build that outputs a lot and then click Home on the keyboard or Page Up or any other key.

After receiving new output page is scrolled to the bottom. And you can repeat this over and over again.

The scrolling behaviour stops if I scroll the mouse wheel but any keypress (page up, page down, home, end, up, down) is keeping messing up the scrolling position.

Do we just have to kill this line?

https://github.com/jenkinsci/blueocean-plugin/blob/b02273dc2a6aee295ac8bd7dbab8eb3a8516a60e/blueocean-dashboard/src/main/js/components/karaoke/components/LogConsole.jsx#L156

This scroll bottom thing hurts more than it helps. It's easy enough for a user to hit fn + right arrow, or the end key...

I'd also note: JENKINS-41088 is a slightly different ask, but could somewhat be accommodated by implementing this. I'll add that after using the tool for a while, I also find myself less interested in following along a particular stage than seeing the graph to click around. At one point, long ago, I did some work to "fix" this behavior somewhat, but it didn't disable following by default. Perhaps I can resurrect the pertinent parts of that if I get some time. Or perhaps a simple button to follow/not follow that's saved in browser storage or something similar would suffice; not sure the right UX for it – suggestions welcome.

This is definitely not resolved, or handled by the referenced issue.

Some builds we run ends up launching 15 parallel tasks (building AMI's for AWS environment), and i want to look at one of these.

The pipeline view's javascript makes it very very hard to select which one of those parallel tasks I want to watch as it's scrolling down to the bottom every few seconds, so i basically have to wait until everything is done (half an hour) before i can even select the right build and see what happened IN THE BEGINNING of this build to figure out what's wrong.

Next, if i manage to pick the correct parallel build it somehow still manages to switch the console output to the output of another build if that one's finished before the one i'm currently watching..

To be honest, this autoscrolling behavior is useless for most of our scenarios as we run a lot of stuff in parallel.

It might be ok to autoscroll-down if the user is already on the bottom of the page and you add more text, but don't mess with where my scrollbar is on the page otherwise. If i want to place it on the middle of the page to investigate something, let me do that. Currently the behaviour prohibits this as it's impossible to do anything but watch the last few lines as long as a build with a lot of text output is running.

Either disable autoscrolling completely or only make it apply whenever a user has scrolled down to bottom.

jamesdumay ditto, my team and I would like to see this auto-scroll behavior disabled.

We find ourselves scrolling back to the top nearly every time we navigate to a failed build from links on Github checks. Further, while the page is loading, the top with the pipeline and menu is shown – it only auto-scrolls to the bottom once the JS or whatever kicks in and loads the console output. This makes the UX disruptive as it jumps us away from where we were getting situated on the page.

We would much prefer if the page did not assume we wanted to be at the bottom of the failed stage's console output, and instead allowed us to navigate where we want to go.

I see that this issue is closed as a duplicate of JENKINS-41088, but I don't think that is quite the same request (per jgamble's comment about a year ago).

We are running Blue Ocean 1.9.0.

Thanks, -j