# nodebb-plugin-composer-quill: WYSIWYG alternative to redactor

• I did notice a few bugs, but they are not very annoying though. (NodeBB docker: latest v1.13.3 / composer-quill: 1.2.1) Edit: composer-quill v1.2.8

• When editing an existing post, if I undo the modification it suggests deleting the post instead of proposing "cancel" (it doesn't delete it)

• The chat mode doesn't work anymore (I wasn't using it, it's always disabled on my instance).

• Sometimes the emoji button does not appear for a new topic.

• When the emoji button appears, emojis can only be added by drag and drop in the text. (I don't know if this is the normal behavior)

• The hypertext urls links already present in posts before quill migration are no longer hypertext links. (not really a bug since it comes from Quill, I assume.)

• I can't undo full screen mode without leaving the composer.

• The text that proposes to write tags of a new topic is truncated in others languages.

• @Per0x thanks for reporting! Those are definitely some "paper cuts" that will need fixing

• @Per0x emoji, actually... Shouldn't have a button at all. Emoji doesn't bind a listener to the formatting bar in a way Quill can read, so the toolbar button should actually be gone are you using the latest version?

• @julian I think so. I installed everything yesterday, under docker (pull tag latest on saturday 23rd may) and ran "npm i nodebb-plugin-composer-quill" the same day in version 1.2.1. However I see that a new docker image (latest) was added 7 hours ago on docker hub. I just need to point out that I've restored a redis backup for the database.

• @julian I do an update and what do I see? Fonts!
Nice! You were fast.
Thank you.

• Heh, no worries.

The recommended way of inserting emoji would be to type :. I think a GUI picker would be nice, but the emoji plugin does not make it dead simple yet

• Don't have poll button, tags menu and switch category menu in composer.
NodeBB v1.15.0

• Hi @togan, I've actually worked on getting the poll plugin compatible with latest Quill. It should be working fine with the latest poll version (v1.1.2)

• Hi @togan, I've actually worked on getting the poll plugin compatible with latest Quill. It should be working fine with the latest poll version (v1.1.2)

Why isn't quill the default composer here?

• Some problems I've discovered after using Quill on my forum for a week:

1. Doesn't work on Safari; the text area is not clickable, fixed by
.composer {
-webkit-user-select: auto;
}


Safari doesn't support user-select property, it needs to be set with -webkit- prefix to override -webkit-user-select: none which is defined earlier in CSS.

1. Automatic conversion of pasted links into <a href> works well, but it's not compatible with nodebb-plugin-youtube-embed, it strips the link of www for some reason (like for youtube links which by default are copied with it), so <href> and the text in the composer are not identical, but even if they are identical the plugin can't transform the link into an iframe. If I simply remove the autogenerated link and make it manually via the composer button all works just fine.

1. When quoting using markdown (Quote button) I have

Username said in thread_name:

quote

It doesn't happen when I'm using Quill, only the actual quote is pasted into the composer. Is this an expected behavior or a bug?

• Hi @julian i'm having a trouble with Quill on 1.13.3. It doesn't show any components, any ideas? Thanks.
![alt text]( image url)

• Hello. Quill does not work with private chat messages by default. Do you have any settings for adding quill to the chat? Or does quill only work with topics?

• @volanar private chat messages? What do you mean?

Quill does actually work with chat, although sometimes the editor doesn't load maybe that's what you're seeing.

I can take a look possibly...

• @volanar The quill composer does actually work in the chat. The toolbar is actually just hidden

You can expose it by highlighting text:

• @julian Thanks. I didn't expect it to work like this. I will check the usability on mobile devices

• I didn't expect it to work like this. I

Me neither! I re-discover it every time someone asks me about it

• @julian Why do you not use it here as the default?

• @torn2 we officially support both but the default composer is default because the Markdown composer is a good low-resource (but high functionality) base composer for all NodeBBs.

Not all communities want or appreciate a WYSIWYG composer.

Also, I like Markdown

4

3

6

3

8
| |