-
Notifications
You must be signed in to change notification settings - Fork 81
Emptying editor does not allow "Save" and leaves artifacts. #50
Comments
Dunno if this will solve all the issues mentioned above, but I got it to save in an empty state by removing |
Thanks, I found this PR can fix the issue |
Hey i already fixed this in my PR. Please merge it, im already using in production :) |
I thought the check for blocks was not needed, just forward the change event and resave
For more info test the PR info for the following usecase
|
@melishev Could you accept this PR, ill have some time soon to complete dark mode |
If an editor field is used once, it cannot be returned to
NULL
or""
.If all content is deleted from the field,
Save
does not light up. And if edits are made elsewhere to bring upSave
, that empty field does not save. The text from the prior state will still be there, rather than""
orNULL
.The only way to empty a field is to directly edit the database.
The text was updated successfully, but these errors were encountered: