Currently there is a race conditions in the UI for editing an item value in a statement: After typing but before the PropertySuggester shows its item suggestions or if the property suggester is not deployed, ESC cancels the edit. If the PropertySuggester shows, ESC only closes the property suggester. So the current behavior is different depending on latency.
One solution is to pass on the ESC from the PropertySuggester to cancel the edit. (Result is that there is no keyboard shortcut to only cancel the PropertySuggester anymore.)
Another solution would be to show the suggester at the same time as showing the edit field and still needing one ESC for closing the pop up and one for canceling the edit.
The PropertySuggester should behave the same way as the EntitySuggester and other popups.
This is also causing failures in the browsertests, since they don't check whether the property suggester is deployed or not.