Zammad: Ctrl+Backspace breaks text module selector

[martinvonwittich]

Infos:

• Used Zammad version: 3.3.x
• Installation method (source, package, ..): docker-compose
• Operating system: Debian 10.3
• Database + version: postgresql 9.6.17 (from docker-compose)
• Elasticsearch version: 7.6.1 (from docker-compose)
• Browser + version: Chromium 80

Expected behavior:

• When you type ::foo to open the text module selector, and then hit Ctrl+Backspace to change ::foo to ::, the text module selector should continue to work normally.

Actual behavior:

• The text module selector behaves very erratically after Ctrl+Backspace.

A short demonstration - using only backspace to delete text works fine and won't break the completion:

But as soon as I press Ctrl+Backspace to delete the whole word at once, the completion behaves very erratically:

Steps to reproduce the behavior:

• Type ::foo, hit Ctrl+Backspace to delete the foo, and attempt to use the completion.

Yes I'm sure this is a bug and no feature request or a general question.

[MrGeneration]

Hey,

is it possible that this is a duplicate of https://github.com/zammad/zammad/issues/2886 ?

[martinvonwittich]

is it possible that this is a duplicate of #2886 ?

Hmm, yes, that could be possible. On my first look at #2886 it seemed to describe a different problem (user wants to leave text module mode, but Zammad silently doesn't, causing data loss on the next return). But the fact that this:

• Type ::foo
• Hit Ctrl+Backspace
• Type bar
• Hit Return

also removes the text bar, just like in #2886, seems to indicate that both issues probably have the same root cause.

[MrGeneration]

Thanks for your feedback.
I'll close this as duplicate in favor of #2886 then.

Your issue should be covered by it, as on mantas comment: https://github.com/zammad/zammad/issues/2886#issuecomment-573119727

At least that's what I believe. :-)