Use trix instead of quill.js

[mrcasals]

As explained in #4873, quill.js is giving us problems. I suggest we move to https://github.com/basecamp/trix, which is the default one in Rails 6 and also would enable us to properly implement #4595, even if we don't use ActiveStorage

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. @carolromero & @xabier feel free to chime in.

[tramuntanal]

Don't close as Rails 6 is coming!

[mrcasals]

@tramuntanal trix is already open-source, so no need to wait for it to start moving the text editors! 😄

[tramuntanal]

Yes @mrcasals but Rails 6 also comes with ActionText that ties Trix with other parts of the framework. But I haven't checked it yet, maybe you are right and development may start without ActionText 😄

I was just wanting to stop the robot from closing the issue

[carolromero]

hey @mrcasals @tramuntanal I'm excited to see activity in this issue, needless to say that it's probably the most desired functionality of Decidim. 😍
@tramuntanal if you take a look at it, do you think it could go into the original request of the Generalitat?

[tramuntanal]

Hi @carolromero , there's nothing related with rich text in CodiTramuntana's current developments :(
but we'll propose it from now on.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. @carolromero & @xabier feel free to chime in.

[ahukkanen]

Is there any active discussion about the Rails 6 upgrade for Decidim?

I am particularly eagerly waiting for the upgrade in order to move to Trix and improve the rich text editor capabilities in Decidim.

[carolromero]

Hello @ahukkanen,

We did discuss it because of this improvement we're making now: #5451
The conclusion was that Trix would indeed be the natural evolution once we upgrade to Rails 6. But it's not clear yet when we're going to do that upgrade. The development team thinks it's best to wait a reasonable amount of time before taking that step.

Maybe @andreslucena or @tramuntanal want to chime in.