RichText field empty is not completely empty after removing content

BarryBlanco commented 4 years ago

The issue occurs while working with: (check one with "x")

[X] app.storyblok.com (CMS - Interface)
[ ] api.storyblok.com (CMS - Content Delivery API)
[ ] mapi.storyblok.com (CMS - Management API)
[ ] capi.storyblok.com (Commerce - API)
[ ] Commerce - Interface

Current behavior: After editing and removing the text inside a richtext field, the prop isn't entirely empty as it leaves behind some empty p-tag. This results in another bad behavior as it then passes the required validator.

Expected behavior: When the field is visually empty in the interface, the prop should be empty.

Steps to reproduce:

Create a content type with a richtext field that is required.
Create the content and fill the textfield.
Edit the content, remove the field and save

sendy34 commented 2 years ago

Yes, same here. Please fix :)

Ellink commented 1 year ago

Any updates on this ?

sendy34 commented 1 year ago

This is also causing issues with ADA scans since sometimes empty Headings are being generated. If we put a check in JSON to see if actual text is empty, that might hurt performance because Text components are used a lot throughout the pages.

pixelmultiplo commented 1 year ago

Buonanotte

Yexan commented 5 months ago

Hey guys,

The issue is still there nearly 4 years later. Is there something we can do to help on this subject?

Right now I've have added a boolean input to the blok to (force to) identify a RichText field as "empty". It's a bit lame but it works (if someone is looking for temporary solution)

storyblok / storyblok

RichText field empty is not completely empty after removing content #383