Emptying editor does not allow "Save" and leaves artifacts.
See original GitHub issueIf 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 up Save
, that empty field does not save. The text from the prior state will still be there, rather than ""
or NULL
.
The only way to empty a field is to directly edit the database.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Workarounds and Limitations: Known issues in IBM ... - Jazz.net
Attempting to open a new row for editing in a module might lead to a row being added that doesn't permit editing. First...
Read more >Creating a storyboard for an RM project - IBM
You can create the frames in your storyboard by using artifacts, such as storyboards, parts and images, or by using drawing elements from...
Read more >Save a copy before editing to prevent changing the original file
Save a Copy lets you download a copy of a file so you can work in it in the cloud without making changes...
Read more >Saving and editing Looks | Looker - Google Cloud
While exploring, you can save your work by saving a Look. This saves all your choices for filters, visualizations, fields, sorting, and so...
Read more >Regular Maintenance Operations - JFrog - JFrog Documentation
However, once all paths pointing to a binary are deleted, the file is actually no longer being used. To make sure your system...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
#41 this branch really works but it needed a minor fix.
If the text field is a required field, it should have given a “required field” warning when the text is deleted.
#59 With the fix I made here, we can overcome this problem without any problems.
Any advance on this?