mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-13 03:13:58 +03:00
[Feature Request]: wysiwyg emoticons #2458
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @reddexx on GitHub (Oct 28, 2021).
Describe the feature you'd like
Please Aktiviate the wysiwyg (TinyMCE) emoticons Plugin in the wysiwyg (TinyMCE) Editor
Describe the benefits this feature would bring to BookStack users
Emojis 😁
Additional context
No response
@reddexx commented on GitHub (Oct 28, 2021):
@ssddanbrown commented on GitHub (Oct 28, 2021):
Thanks for the request.
I wouldn't look to integrate any custom emoticons in BookStack as I'd prefer to keep content related to widely-supported standards. In addition, we'd be looking to move away from TinyMCE soon (As per #2738) so I won't be activating this plugin & toolbar item.
We can support standard emoji but there's no confirmed nice web standard for selection of such characters right now. That said, most operating systems have an emoji picker built in to them. I know Windows, Android, iOS and Mac all have such emoji picker support. Think it's becoming a supported feature in some linux systems now.
Personally I don't think a custom picker implementation, in addition to using up another editor toolbar space, would be worth it. Happy to hear the case for these though if it'd be significantly solving a problem.
@reddexx commented on GitHub (Oct 28, 2021):
I want to make it easier for my co-users to use emojis.
I know Bookstack is not a chat platform. only often do I use emojis for programming my DiscordBot that I use in
Take unicode
It's just easier with a menu
@ssddanbrown commented on GitHub (Oct 31, 2021):
Okay, Thanks for confirming. Again, I don't really think there's enough reason to implement and maintain a full emoji picker within the application since operating systems already fill this gap in a way that would handle various issues much better than we'd be able to handle (Internationalization, Unicode updates/changes etc...). So will therefore close this off as out of scope.