It seems to me that the debug window has 2 different scrolling behaviors, depending on when it is opened relative to the accumulated debug messages:
A. If you open the Debug window when less than 1 "page" of debug messages have accumulated, or if you open the Debug window, then click the "clear log" (trash can) button: when it fills with debug messages, the Debug window scroll "thumb" will default to the bottom end of the scrollbar, and the newest Debug message will always appear at the bottom of the window. This is the way I would like the Debug window scrolling to always function.
B. If you open the Debug window after more than 1 page of debug messages have accumulated (say, after launching NR in browser, and a flow has auto-started and generated a bunch of debug messages), the Debug window scroll thumb will default to the top end of the scrollbar, and the oldest Debug messages will be "pegged" in the window, until finally the Debug window message buffer is full, and newer messages start scrolling into view.
The latter behavior is undesirable. If you are paying close attention, you will notice that the timestamps of the debug messages scrolling into view are older - not the latest debug messages. And of course, after you notice this, you can simply drag the scroll thumb down from the top to the bottom of the scrollbar, so you get the "A" behavior, and always see newest debug messages at the bottom of the window.
But I have been bitten by "B" more than once. I make changes to a flow, deploy it, and start watching the debug window - but it will appear as if my change has not taken effect, because I am seeing old debug messages scroll into view; not the new debug messages associated with my flow changes.
It is annoying to have to drag the scroll thumb to the bottom when "B" happens.
Could the Debug window scroll behavior be changed, to always default to behavior "A" ?