mirror of https://github.com/zulip/zulip.git
ec25310654
Now checking for custom trigger keys will happen during `keydown` instead of `keyup` so that if the key is printable, `preventDefault` can prevent it from appearing in the compose box. This fixes the case when jumping to topic, would eat up any space or new line after the cursor, due to wrong splitting around the cursor, which was a result of using the printable custom trigger key, the ">", in contrast to a non printable one like Enter. The problem was that custom trigger keys like `>` that the browser's default behavior is to type (vs. others like RightArrow where that isn't the case) can result in extra characters being emitted, which is not wanted. |
||
|---|---|---|
| .. | ||
| bootstrap | ||
| bootstrap-tooltip | ||
| bootstrap-typeahead | ||
| jquery-idle | ||
| marked | ||