# List of all features needed before CSS BAN

**URL:** https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998
**Category:** Feature Requests
**Created:** [July 6, 2022, 9:27pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998 "2022-07-06T21:27:05Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [July 7, 2022, 12:50am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/7 "2022-07-07T00:50:39Z")

</div>

An update:

> [@warning Unsupported HTML/CSS in the Rich Text component will completely break in the coming weeks](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/85):
>
> Hi Matt and other people that have been using our Notion, From David and Mark’s comments, I see that the DOM structure will change, but they will not disable custom CSS. Me and other people will definitely spend time to update our Notion docs so that the old code will work with the new DOM, that’s the best we can do. Let’s say previously, just for the sake of an example, a [data-test="app-vertical-list"] would now become something like [data-test="app-list"] \> div[class="vertical"]. We will t…

---

_[View the full topic](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998)._