Bastelstube
/
Tims-Chat
mirror of https://github.com/wbbaddons/Tims-Chat.git
1
0
Fork 0
Code Issues Releases Wiki Activity
43 Commits 3 Branches 25 Tags 4.7 MiB
Commit Graph

12 Commits

Author SHA1 Message Date
Tim Düsterhus 5fce0c092c
Send the tmpHash instead of the attachmentId 
All the PHP goodies reside inside the AttachmentHandler which expects the
tmpHash.
 2020-11-01 16:24:57 +01:00
Tim Düsterhus 9a870f3f94
Wire Chat.js to Attachment/Upload.js 2020-11-01 16:24:46 +01:00
Tim Düsterhus baa654a37a
Relay the attachmentId in `send` event 2020-11-01 16:24:45 +01:00
Maximilian Mader d5195c0562
Implement attachment upload UI skeleton 2020-11-01 16:24:43 +01:00
Tim Düsterhus 931b01a4bf
Remove unused import in Ui/Chat.js 2020-10-31 19:05:01 +01:00
Tim Düsterhus 17468c9cf6
Make Ui/Input/Autocompleter less of a hack 2020-10-31 17:05:30 +01:00
Tim Düsterhus 7538639d7b
Bump version 2020-10-20 18:03:04 +02:00
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