# ⚠️ Unsupported HTML/CSS in the Rich Text component will completely break in the coming weeks
**URL:** \
**Category:** General\
**Created:** [July 5, 2022, 7:29pm UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931 "2022-07-05T19:29:34Z")\
**Posts on this page:** 1\
**Showing post:** 127
**Author:**  [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [August 20, 2022, 2:02pm UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/127 "2022-08-20T14:02:40Z")
> [@L.M](#):
>
> How would you articulate the changes that experts & no code agencies here have to answer to their customers? How would you recommend them to officially “sell” the future advantages to show how much they will gain as compared to lose, for example.
> Everything on performance, sustainability, compatibility, integration of external tools…?
It turned out to be not as bad as we first thought…
> [@Custom CSS - No, the sky is NOT about to fall in](https://community.glideapps.com/t/custom-css-no-the-sky-is-not-about-to-fall-in/44107):
>
> TLDR; For those amongst us that generally only use CSS for minor tweaks, there is most likely nothing to worry about. Since the [announcement](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931) from David a couple of days ago, there has been quite a stir and a lot of discussion about what is and isn’t supported, and what will and will not break. Fortunately, I’ve been lucky enough (along with a few others) to be able to preview and test the changes on some of my apps. This topic is a summary of what I’ve found. But first, the important stuff… …
---
_[View the full topic](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931)._