Megabit / Blazorise

Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Tailwind, Bulma, AntDesign, and Material.
https://blazorise.com/
Other
3.31k stars 534 forks source link

[Bug]: Richtext edit no longer works in 1.5 #5376

Closed blenke closed 8 months ago

blenke commented 8 months ago

Blazorise Version

1.5

What Blazorise provider are you running on?

Bootstrap5

Link to minimal reproduction or a simple code snippet

After upgrading to 1.5 my RichtTextEdit renders incorrect, also on your the blazorise example page , see: https://blazorise.com/docs/extensions/richtextedit

Steps to reproduce

https://blazorise.com/docs/extensions/richtextedit

What is expected?

layout as in previous versions

What is actually happening?

layout distorted and icons are huge

What browsers do you see the problem on?

Chrome, Microsoft Edge

Any additional comments?

No response

panmona commented 8 months ago

Additionally to that our quill modules seem to have stopped working correctly. Do you have any guidance on how we need to update those? We use modules/blotFormatter, modules/better-table, modules/imageCompress and modules/mention.

stsrki commented 8 months ago

@njannink Can you help?

njannink commented 8 months ago

@panmona we migrated to QuillJS 2.0, because the old QuillJS had a number of security issues and was very old. So maybe because of that those quill modules stopped working. I would see if there are also updates for your modules and otherwise contact the creators of the modules that you are using

https://quilljs.com/guides/upgrading-to-2-0

panmona commented 8 months ago

Thanks. We already used Quill 2.0 before this update (but in a previous version: v2.0.0-dev.4, which is now also already quite old) so that could be an issue. Unfortunately the modules used don't seem to have been gotten an update. I'll check again whether it works once the theme fix is there 👍

It would be nice if changes like that would be highlighted more prominently in the release notes in the future: "No breaking changes" is not true in this case unfortunately.