ADefWebserver
commented
7 months ago I am not sure if this component should be upgraded. Perhaps a new component should be created instead. However, what issues did you see when you updated to Quill 2.00?
Closed Markus243 closed 6 months ago
ADefWebserver
commented
7 months ago I am not sure if this component should be upgraded. Perhaps a new component should be created instead. However, what issues did you see when you updated to Quill 2.00?
markushaslinger
commented
6 months ago However, what issues did you see when you updated to Quill 2.00?
A simple replacement of the js & css files to current quill 2.0.1 gave me the following error:
Cannot read properties of null (reading '__quill')
at Object.loadQuillHTMLContent (http://localhost:5204/_content/Blazored.TextEditor/Blazored-BlazorQuill.js:40:33)@markushaslinger A new Blazor component would need to be created from scratch to work with Quill 2.0
ADefWebserver
commented
6 months ago @markushaslinger A new Blazor component would need to be created from scratch to work with Quill 2.0
Describe the bug A clear and concise description of what the bug is. Using the cdn's 1.3.7 as per the documentation I encounter: [Deprecation] Listener added for a synchronous 'DOMNodeInserted' DOM Mutation Event. This event type is deprecated () and work is underway to remove it from this browser. Usage of this event listener will cause performance issues today, and represents a risk of future incompatibility. Consider using MutationObserver instead.
To Reproduce Steps to reproduce the behavior:
Hosting Model (is this issue happening with a certain hosting model?):
Additional context I tried updating to later versions of QuillJs >2.00 but this seems to break compatibility with blazored texteditor. Any help/solutions or workarounds would be greatly appreciated.