You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quill.getBounds function fails with error Uncaught TypeError: leaf.domNode.getBoundingClientRect is not a function when try to use the library inside the LWC in Salesforce
quill.js:2963 Uncaught TypeError: leaf.domNode.getBoundingClientRect is not a function
at Selection.getBounds (quill.js:2963)
at eval (eval at getBounds (quill.js:1), <anonymous>:1:16)
at Quill.getBounds (quill.js:1264)
at Repro.onTextChange (repro.js:63)
at Emitter.emit (quill.js:8571)
at Emitter.emit (quill.js:1893)
at Quill.modify (quill.js:1628)
at Emitter.eval (quill.js:1122)
at Emitter.emit (quill.js:8570)
at Emitter.emit (quill.js:1893)
Steps for Reproduction
Create LWC component with the following code
repro.html:
Open debugger and set breakpoint on line this.quill.getBounds(0);
Input any character into container.
In the debugger javascript console try to execute code this.quill.getBounds(0);
See the errror
Expected behavior:
There should not be an error when quill library is added to Salesforce LWC component. Actual behavior:
It fails Platforms:
Salesforce LWC. Chrome, Mac
Version:
"1.3.6"
The text was updated successfully, but these errors were encountered:
Quill 2.0 has been released (announcement post) with many changes and fixes. If this is still an issue please create a new issue after reviewing our updated Contributing guide 🙏
Quill.getBounds function fails with error Uncaught TypeError: leaf.domNode.getBoundingClientRect is not a function when try to use the library inside the LWC in Salesforce
Steps for Reproduction
repro.html:
repro.js:
repro.js-meta.xml:
this.quill.getBounds(0);
this.quill.getBounds(0);
Expected behavior:
There should not be an error when quill library is added to Salesforce LWC component.
Actual behavior:
It fails
Platforms:
Salesforce LWC. Chrome, Mac
Version:
"1.3.6"
The text was updated successfully, but these errors were encountered: