Before I make a github issue, I would like to share my observations. This may be a browser issue.
When I open a Sage worksheet with lots of text output, then many of those output cells appear as a single blank line when the worksheet is first opened, and then the actual output will show up as the browser processes things. Since this output is usually longer than one line, rendering the actual output results in later parts of the page being moved down. (Plots may cause similar behavior, since they are often delayed as well, but I didn't check this extensively).
When I click on an early line (above the point where any shifting has occurred), then the cursor appears right where I clicked. However, if I click on a later line, then the cursor will jump several lines below where I click. It appears that the jump size increases as I go further down the page. It may be (but I'm not sure) that the amount of jump depends on the size of the shift resulting from the rendered output.
This only happens on the first such click. After this, everything works as expected.
I also noticed that the original cursor position also shifts. For example, if I have the cursor on line 100 when I close the worksheet, then when I re-open the worksheet the cursor begins at line 100. But then line 100 gets shifted down the page due to output above that showing up. Instead of the cursor staying with line 100 as it moves, the cursor stays in the same spot. So as the lines move down, the cursor may end up in line 90; it may even end up in the middle of an output cell.
I don't know if this issue is caused by the browser (I tried both Chrome and MS Edge), or if it has to do with my connection speed (my ping times are 100-125ms on a good day - is that typical?).
Here is an example of the kinds of worksheets I use:
I will create a github issue if you think something can be done from the SMC side. This is not a high priority, just an irritation at this point.
Thanks,
Aaron