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
What is the current behavior?
This seems to be specifically an issue caused by this wrapper, since it is not reproducible in the tinymce fiddle environment.
The issue is that when the editor has a v-model value then the content gets "refreshed" on some actions:
Cursor_jump.mov
Write text and add space at the end (the space is important)
Use shortcut (CTRL + B, CTRL + U or CTRL + I)
Write text
???
Cursor jumps to the beginning of the editor
Please provide the steps to reproduce and if possible a minimal demo of the problem.:
When v-model is removed, and one variable is used for "initial content", which is passed to the :model-value, and a event listener is added to the @update:model-value event to update the "main data variable" then it works.
But it is very counter intuitive to have to use a variable for initial content and another for actually storing the data.
What is the current behavior?
This seems to be specifically an issue caused by this wrapper, since it is not reproducible in the tinymce fiddle environment.
The issue is that when the editor has a
v-modelvalue then the content gets "refreshed" on some actions:Cursor_jump.mov
???
Please provide the steps to reproduce and if possible a minimal demo of the problem.:
https://codesandbox.io/p/devbox/dazzling-albattani-27yf8g
What is the expected behavior?
Cursor stays at the same location.
Which versions of TinyMCE, and which browser / OS are affected by this issue? Did this work in previous versions of TinyMCE or tinymce-vue?
Atleast:
"@tinymce/tinymce-vue": "^6.3.0",
"vue": "^3.5.22",
Chromium based browsers.
Pretty sure it used to work at some point :D
When v-model is removed, and one variable is used for "initial content", which is passed to the
:model-value, and a event listener is added to the@update:model-valueevent to update the "main data variable" then it works.But it is very counter intuitive to have to use a variable for initial content and another for actually storing the data.