5 Commits

Author	SHA1	Message	Date
Tim Düsterhus	5687d6fabb	Bump version	2020-03-25 23:04:48 +01:00
Tim Düsterhus	560b010a65	Prevent the copy handler from unveiling tombstoned messages	2020-03-25 23:01:20 +01:00
Tim Düsterhus	26f2679841	Bump version	2018-11-27 20:53:30 +01:00
Maximilian Mader	724540a8b2	Fix enter key check while composing characters ... Chrome on macOS sends a KeyEvent with `key` set to `Enter`, the keyCode `229` and `isComposing` set to `true` when pressing enter while a character composition sequence is active, then an event for the composed key and ends with a Enter key event with the correct key code. This has thrown our Enter key detection off and resulted in sending of the wanted message and a public message with the single composed character as content. Ignoring the Enter key while characters are being composed seems to be safe.	2018-08-22 19:18:09 +02:00
Tim Düsterhus	317ee29461	Initial import	2018-08-17 00:30:59 +02:00