Indeed, it is not resolved.
Having looked into this issue again, I find the following:
Generally speaking, the problem stems from the fact that Tersus dialogs do not block keyboard events from being handled by the dialog's ancestor.
More specifically, here are some scenarios:
We shall try to implement a solution for these scenarios, in one of the coming updates.
For best results, use the Firefox browser..