I tried searching for similar issues but everything I could find was marked 'Closed' and considered fixed in previous versions. Sorry if I have missed something

Seeing some weird behaviour with the 'Execute current line' and 'Shift-F5' commands that I'm hoping you can help me figure out.

In 3.10.1 if I had multiple statements on separate lines with semi-colons I could put the cursor on query 1 and 'Execute current line' to only run that statement.
In 3.11.0-beta1 I'm getting two different behaviours depending on the structure of query 1

• Query 1 is only a single line with semi-colon (example: select * from table;) executes that query but then proceeds to execute next statement as well
• Query 1 is split into multiple lines results in an error unless cursor is on first line of statement. Considering that I'm likely to be on the last line of the query (as that is what I have just typed) when I'm executing the line it seems weird that I have to move the cursor back to the first line before executing. Previous versions were able to find the start of the query properly.

Am I missing something?
Appreciate any help