Selecting a lot of code in the same line causes script-editor window to scroll too fast or undesirably

[un1ND3X (ice)]

While selecting/ highlighting a lot of code in the same line and moving the cursor towards a certain direction to highlight another part which is close to the editor frame boundary, the canvas scrolls undesirably too fast or just moves the cursor some place else, this did not occur before the new script editor updates, and was tested through a laptop

Video of the bug occurring:

While trying to select code from the other side, the canvas just scrolls too fast regardless of how little the cursor ever goes off spot.

It can be avoided by normally using the scrollbar.

The exact date this bug started occurring is not known, but I believe I didn’t encounter anything like this before the new script-editor updates.

To Reproduce:

create a script with the following code:

 local abc  = "abcabcabcab_cabcabcabc_abcabcabc_abcabcabc_abcabcabca_bcabcabca_bcabcabcabc_abcabcabcabca_bcabIabcabc_abcabcabcabca_bcabcabcabcbcabcabcabcbcabcabcabcbcabcabcabcbcabcabcabcbcabcabcabc"

for the ease of reproduction, the window needs to be resized like this

Trying to select the string from the left where it starts entirely towards the I will be difficult.

[tralalah]

I think part of it is intentional - if you are looking to highlight further, it’s a waste of time to see the screen keep moving along. The reason it pops back is because you are moving the cursor to the line above or below. I’m pretty sure for highlighting long snippets, it’s beneficial to break the line into multiple lines in the first place, or just use the scroll wheel ahead of time. I’m not sure what sort of fix could be proposed without ruining someone else’s workflow.

[Kryptonnik]

I reccomend using Control+A instead, sometimes scrolling while editing messes up lines of code and causes script errors.

[Hippie_ofDoom]

Thanks for the report! We’ve filed this internally and we’ll follow up here when we have an update for you.

[Hippie_ofDoom]

I am in the process of checking over bug reports and following up on some bugs that haven’t received any activity in a while.
Is this issue still occurring or can you confirm that this bug has been resolved?

[Hippie_ofDoom]

This issue should now be resolved! If this issue is still occurring, please create a new topic for us to look into.