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
Hi, I have the same problem in 3.0.12, when editing a markdown field (but not all), the browser crash on this error.
I can't find what differs between this field and others.
Here are the console logs
Error: Cannot resolve a DOM node from Slate node: {"text":""}
toDOMNode https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
toDOMPoint https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
toDOMRange https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
r https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
ln https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
us https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
cs https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Ol https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
unstable_runWithPriority https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Vi https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Tl https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
hl https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Yi https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
unstable_runWithPriority https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Vi https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Yi https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
Zi https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
ml https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
onChange https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
apply https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js:485
decap-cms.js:485:2244126
Describe the bug
To Reproduce
Expected behavior
Screenshots
Applicable Versions:
decap-cms@3.0.12
github
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36
CMS configuration
The text was updated successfully, but these errors were encountered: