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
Then re-using the same component that locally registers vue-quill-editor, the toolbar styles (snow-theme) are not loaded after visiting a few routes where the editor is mounted. The toolbar is rendered with default html styles.
How are toolbar styles loaded? It seems like there is some race condition here, or it could be that there is some global registration going on? Is vue-quill-editor registered with the Vue instance or something?
Reproduction
Based on the example from the readme, but with custom icon overrides this error occurs on subsequent loads of the component when used in a drawer thats conditionally rendered. In running the component it appears the ref to the quill editor cannot be found when printing the message in the ``mounted()hook i get the following: [Vue warn]: Error in mounted hook: "TypeError: this.$refs.myQuillEditor is undefined"`
Describe the bug
Then re-using the same component that locally registers vue-quill-editor, the toolbar styles (snow-theme) are not loaded after visiting a few routes where the editor is mounted. The toolbar is rendered with default html styles.
How are toolbar styles loaded? It seems like there is some race condition here, or it could be that there is some global registration going on? Is vue-quill-editor registered with the Vue instance or something?
Reproduction
Based on the example from the readme, but with custom icon overrides this error occurs on subsequent loads of the component when used in a drawer thats conditionally rendered. In running the component it appears the ref to the quill editor cannot be found when printing the message in the ``mounted()
hook i get the following:
[Vue warn]: Error in mounted hook: "TypeError: this.$refs.myQuillEditor is undefined"`System Info
Used Package Manager
yarn
Validations
The text was updated successfully, but these errors were encountered: