Grok proccessor UI bug

Yep, this works fine.
So what's the reason for different behavior between Grok Debugger and Grok Processors with escape characters?