tscherler michaelneale fyi, follow-up from JENKINS-41885

tsniatowski would you be using Edge or Internet explorer? JENKINS-46632 is a report for double scrollbars.

I'm also seeing the double scrollbars. I'm using Chromium (61) using Ubuntu/Cinnamon Desktop.
The one nearest the right edge is disabled though, as in it just appears but it does not do anything.
I also see points 2 and 3
I can't see point 4, my blue ocean does update the logs after scroll up but it does not auto follow again.
I'm currently at the point where I tend to not want to look at steps in progress since the UX is annoying me. I typically click on some step that's complete to get UI to stop jumping. Actually good to know about the mousescroll, I always use PageUp and this has annoyed med the most.

jdumay I see these issues on Firefox 55 and Chromium 61 on Linux (Ubuntu), except for 4 as mentioned above which may have been a one-time fluke or just confusion on my part.

There are two vertical scrollbars in Blueocean for some reason

fkykko tsniatowski can we please get a screenshot of this and have it reported in another ticket?

Blueocean does not stop scrolling in all cases where the old UI would. JENKINS-41885 made it stop the auto-scroll-on-update on a mouse-wheel scroll, but grabbing the slider and scrolling up by that does not stop the auto-scroll, resulting in a poor user experience. Old UI would stop in that case. Same deal with PgUp/ Home key presses.
It is not possible to make Blueocean resume auto-scrolling. Old UI resumes auto-scrolling when the view is moved back to the last displayed log.
It even seems like Bluoecean stops updating, not just auto-scroling on the mouse-wheel scroll, requiring a page refresh to see new logs after the user has scrolled up.

I suspect you've been bitten by this bug JENKINS-44342 (scheduled)

I tested the pageup/pagedown keys - you are right that they don't work. Ive raised JENKINS-47654 to fix.

There's a misleading "complete log" link at the top which leads to a truncated log when the build is in progress (in my test the dynamic view is at log line 22000, "complete log" ends at 9700). The old UI defaults to a partial view with live updates and has a "full log" link to a full view also with updates, so this new behavior is surprising.

The complete log is for the step you are focused on. The full log of the entire pipeline run can be found under "Artifacts" as "pipeline.log".

Testing Notes:

• Page Up / Page Down support ended up in its own ticket, JENKINS-47654.
• Testing to verify the behaviors described by cliffmeyers
  in this comment from JENKINS-44342 are probably best done with a manual, visual check.

Re double scrollbar, I commented in JENKINS-46632 and posted a screenshot. It looks exactly the same.

Re JENKINS-44342: possible, it did happen a couple more times for me that the auto-updates did not resume.

Re complete log: what irks me that in my case I have a single long build step, that will output some 20k lines of log. The auto-updating log at
JENKINS/blue/organizations/jenkins/foo/detail/foo/2426/pipeline/ is at line 17k, but the "complete log" from JENKINS/blue/rest/organizations/jenkins/pipelines/foo/runs/2426/log/?start=0 ends at line ~10k. If I remove the "start=0" component, I get a non-updating snapshot of the log at `17k-odd lines – still not "complete". I can f5 to get 17k-odd-plus-some, not very convenient.

Note that the old jenkins UI did have an updating display when you clicked on "full log", so this is misleading. Frankly I'm a bit sad BO reimplements something (from a purely user perspective) that was working "fine" and has so many teething issues.