Open wsiota opened 2 years ago
It's been a while since we last heard from you. We are marking this issue as stale due to inactivity. Please provide the requested feedback or the issue will be closed after next 7 days.
Hello, @wsiota, thanks for the report and I'm sorry for the late reply.
I see, that even giving a zero-latency timeout in the instanceReady()
method for a model update solves the problem. 🤔
For now, I can confirm this issue.
Are you reporting a feature request or a bug?
Bug
Provide detailed reproduction steps (if any)
https://codesandbox.io/s/ckeditor4-vue-bug-report-v-model-timing-window-issue-s83ys2
instanceReady
CKEditor event is emitted (or close to this timing window).Expected result
CKEditor should show the updated model value ("new value").
Actual result
CKEditor shows the original model value ("initial value").
Other details
Additional Notes
input
event?). This means that the "new value" is lost!We hit this by populating the CKEditor contents upon a page load from an async call (using v-model). It is not consistently reproducible in our app as it depends on hitting what seems to be a narrow timing window. But the provided CodeSandbox appears to consistently reproduce this by changing the v-model on the
instanceReady
event.This could be related to #50.