-
Story
-
Resolution: Unresolved
-
Major
-
-
Blue Ocean 1.1, Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2, Blue Ocean 1.6 - beta 2, Blue Ocean - 1.6 - beta 4
Steps to reproduce
- I am viewing the running Pipeline defined in the example below
- Step 1 of stage 1 is executing. I select its text with my mouse to copy and paste or interact with the log in some way (selecting, clicking, etc - I am focused on this log as its streaming)
- Step 1 of stage 1 finishes and Step 1 of Stage 2 starts executing
- My focus is ripped away from Step 1 of Stage 1 to Step 1 of Stage 2.
What should happen
When I open step 1 of stage 1, karaoke should not move my focus to Step 1 of Stage 2.
Example
pipeline { agent any stages { stage('1') { steps { sh 'ping -c 10 localhost' } } stage('2') { steps { sh 'ping -c 50 localhost' } } } }
- is related to
-
JENKINS-44342 Karaoke does not resume after "scroll to bottom"
-
- Closed
-
Piggy-backing on this, it would be cool if pressing the "HOME" key (which scrolls browser to the top) also disabled karaoke.
I wonder if it would be easier to code the logic so that a mouse event or keyboard event stops karaoke, except in the following cases:
Maybe also on a mouse click that isn't an interactive element. It's hard to say which approach is the right way, but it feels like most of the time when the user begins interacting that it's safe to assume we should stop scrolling. I could be wrong, but thought it was worth discussing.