Bug in the SQL reference (CTRL + F1)

Try this to understand this bug:

1. Type CASE and hit CTRL F1 to get Reference Prompt
CASE input_expression WHEN WHEN_expression THEN result_expression.
2. If While the 'CASE' prompt box is up, I change the 'input_expression', Then click on 'when_expression' on the reference prompt with the intention to highlight the 'when_expression' in my code, it highlights the 'old' area in my code where 'when_expression' used to be but has obviously moved because I changed 'input_expression' to an actual value.

Thanks.

Hello sysadmin, any thoughts on this matter appreciated.
Cheers

Well, I am not sure whether it is a bug or by design, in other words, just how it works in the current version. Don't expect SQL Reference to be able to read all text completely in all editors and be able to reparse it so it can separate what it has inserted into the editor from what was typed by users. As for the thing you described, we are looking into this issue and checking if we can make incremental improvements.

For now, the proper way to use SQL Reference is to paste the complete command syntax and then edit names and options placeholders between pasted keywords.

We are planning significant changes in the parsing algorithms and making major improvements in this area in version 2.