# ⚠️ Unsupported HTML/CSS in the Rich Text component will completely break in the coming weeks

**URL:** <https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931>\
**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:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [July 6, 2022, 12:57am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/22 "2022-07-06T00:57:55Z")

</div>

oooh, this is not what I wanted to wake up to on a Wednesday morning, ouch 😬

I guess the upside is that this probably means that Apps are about to be switched to NCM.

---

<div class="post-metadata">

**Author:** ![fluittsolutions](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/fluittsolutions/32/30155_2.png) [@fluittsolutions](https://community.glideapps.com/u/fluittsolutions)\
**Post date:** [July 6, 2022, 1:11am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/23 "2022-07-06T01:11:57Z")

</div>

@Darren_Murphy what is “NCM?”

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [July 6, 2022, 1:14am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/24 "2022-07-06T01:14:42Z")

</div>

> [@NCM - what is it and why do Glide Experts keep mentioning it?](https://community.glideapps.com/t/ncm-what-is-it-and-why-do-glide-experts-keep-mentioning-it/43387/2):
>
> The computation model is the underlying code that makes glide work. Basically the original computation model is what Apps currently run on and is hard to maintain and not necessarily efficient code. When Glide added pages, they rewrote the underlying code from the ground up, so currently Pages uses the new computation model. They are now working to convert Apps to that new updated code. From our standpoint, it really shouldn’t mean much to us, other than some things will most likely run more…

---

<div class="post-metadata">

**Author:** ![fluittsolutions](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/fluittsolutions/32/30155_2.png) [@fluittsolutions](https://community.glideapps.com/u/fluittsolutions)\
**Post date:** [July 6, 2022, 1:14am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/25 "2022-07-06T01:14:53Z")

</div>

While I feel the pain of those of you that will lose something you have built into your apps, I am glad for adding more tools to stick with the no-code concept. I have posed several questions in the community that others have suggested CSS to accomplish what I wanted to do. But CSS is beyond my skill set. I don’t want to add any kind of code to a no-code platform.

---

<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 6, 2022, 1:16am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/26 "2022-07-06T01:16:34Z")

</div>

> [@Darren\_Murphy](#):
>
> I guess the upside is that this probably means that Apps are about to be switched to NCM.

Yeah, I guess so. Can still do some certain things with HTML, but without styling, like what we have made do with Pages in recent months (not the tables formatting).

---

<div class="post-metadata">

**Author:** ![justinjmp](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/justinjmp/32/43205_2.png) [@justinjmp](https://community.glideapps.com/u/justinjmp)\
**Post date:** [July 6, 2022, 1:28am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/27 "2022-07-06T01:28:34Z")

</div>

While a change that will take work to get around, ultimately it’s a decision that has to be made if it’s the direction that Glide wants to go after.

@david with changes like this one, new pricing plans, and the view on data sources, it would be nice to hear more about the ultimate target user of Glide. Ultimately this change won’t impact the vast majority of users but will affect power users, specially people active on this community. It would be nice to hear more about the vision and where Glide would like to position itself amongst new, target, and power users on the platform.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [July 6, 2022, 1:37am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/28 "2022-07-06T01:37:30Z")

</div>

> [@justinjmp](#):
>
> it would be nice to hear more about the ultimate target user of Glide

This has not changed in the three years we’ve been working on Glide, and I explain it the same time every time I’m asked–Glide is for non-technical people (who don’t know how to code, including CSS) building apps to be used internally within their company, or by their customers.

And from day one, we’ve warned that this hack inside the Rich Text component was unsupported and would one day break. That day is coming soon! This doesn’t represent a change in who Glide is for, for example–it’s purely an unrelated technical change that happens to close this loophole by accident.

---

<div class="post-metadata">

**Author:** ![justinjmp](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/justinjmp/32/43205_2.png) [@justinjmp](https://community.glideapps.com/u/justinjmp)\
**Post date:** [July 6, 2022, 1:46am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/29 "2022-07-06T01:46:22Z")

</div>

Thank you that makes a lot of sense

---

<div class="post-metadata">

**Author:** ![resepsionis\_ganteng](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/resepsionis_ganteng/32/39081_2.png) [@resepsionis\_ganteng](https://community.glideapps.com/u/resepsionis_ganteng)\
**Post date:** [July 6, 2022, 1:58am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/30 "2022-07-06T01:58:32Z")

</div>

for me css is an alternative to make the application look more attractive.

if the glide party will stop this, it would be nice if Glide also provides options or features such as making designs manually or components available by Glide.

---

<div class="post-metadata">

**Author:** ![wjcv06](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wjcv06/32/12747_2.png) [@wjcv06](https://community.glideapps.com/u/wjcv06)\
**Post date:** [July 6, 2022, 2:08am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/31 "2022-07-06T02:08:07Z")

</div>

I think the use of CSS was what really made the difference, what a pity ☹

---

<div class="post-metadata">

**Author:** ![Lisa](https://avatars.discourse-cdn.com/v4/letter/l/f08c70/32.png) [@Lisa](https://community.glideapps.com/u/Lisa)\
**Post date:** [July 6, 2022, 3:04am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/32 "2022-07-06T03:04:02Z")

</div>

I knew this day was coming, HUGE thank you for the heads up!

---

<div class="post-metadata">

**Author:** ![resepsionis\_ganteng](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/resepsionis_ganteng/32/39081_2.png) [@resepsionis\_ganteng](https://community.glideapps.com/u/resepsionis_ganteng)\
**Post date:** [July 6, 2022, 3:27am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/33 "2022-07-06T03:27:58Z")

</div>

Discontinuing Custom CSS means we will lose all the alternatives that have been discussed in this forum.

Not just the html style but the **notification alternatives** we need the most will also be missing.  
Stop css for reasons of speed performance still _mind_.

_we also need another solution. which we have **solved** in this forum._

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [July 6, 2022, 5:41am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/34 "2022-07-06T05:41:29Z")

</div>

> [@ThinhDinh](#):
>
> Yeah, I guess so. Can still do some certain things with HTML, but without styling, like what we have made do with Pages in recent months (not the tables formatting).

I guess we’ll just have to start using Cloudinary to build nice looking dynamic HTML tables. Now, _there_ is a challenge!! 🤣 🤪

---

<div class="post-metadata">

**Author:** ![11183](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/11183/32/29797_2.png) [@11183](https://community.glideapps.com/u/11183)\
**Post date:** [July 6, 2022, 5:52am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/35 "2022-07-06T05:52:43Z")

</div>

Recently I found out that Markdown actually has its own extended syntax for tables. But it doesn’t work in Rich Text(

> **[Markdown Table Editor and Generator - Table Convert Online](https://tableconvert.com/markdown-generator)**
>
> This online generator is used to quickly make, create and generate Markdown Table. You can also edit Markdown Table using Excel-like table editor.

---

<div class="post-metadata">

**Author:** ![grumo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/grumo/32/34786_2.png) [@grumo](https://community.glideapps.com/u/grumo)\
**Post date:** [July 6, 2022, 6:25am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/36 "2022-07-06T06:25:30Z")

</div>

Thanks, I used it for my AirBNB clone app. It’s a pity it will soon die ☹

---

<div class="post-metadata">

**Author:** ![Roldy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/roldy/32/36068_2.png) [@Roldy](https://community.glideapps.com/u/Roldy)\
**Post date:** [July 6, 2022, 7:44am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/37 "2022-07-06T07:44:16Z")

</div>

I knew that this day would come sooner or later and, fortunately, I did not want to insist too much with the implementation of CSS, but I have to say reluctantly because it is a language that I know quite well and that in certain circumstances it was perfect to make up for some layout. And, in my opinion, also not to make all the apps too similar.  
I expect, and hope, that new no-code tools will be implemented to achieve similar goals.  
Congratulations to Glide in any case, because improving performance and simplicity is undoubtedly more important 👏

---

<div class="post-metadata">

**Author:** ![Gregory](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gregory/32/21180_2.png) [@Gregory](https://community.glideapps.com/u/Gregory)\
**Post date:** [July 6, 2022, 7:54am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/38 "2022-07-06T07:54:17Z")

</div>

@david : Will there be alternatives to most CSS-based workarounds (e.g. good looking tables with \>2 columns) ?  
If yes, when?

---

<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 6, 2022, 8:12am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/39 "2022-07-06T08:12:29Z")

</div>

> [@Roldy](#):
>
> And, in my opinion, also not to make all the apps too similar.

Yeah, this was my main reason for using CSS. I hope this mean a step up in some certain components that we used to have to get help from CSS.

---

<div class="post-metadata">

**Author:** ![Frankchavezbernal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/frankchavezbernal/32/41891_2.png) [@Frankchavezbernal](https://community.glideapps.com/u/Frankchavezbernal)\
**Post date:** [July 6, 2022, 11:14am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/40 "2022-07-06T11:14:06Z")

</div>

Good evening, what I can’t understand is how glide wants to be able to innovate with applications if we lock our clients with minimal visual project creation options  
What I think would have been ideal is to add more components that can enrich the projects and remove the css and html since it compensates in a way to be able to generate projects that make a difference to the projects that we commonly see, but well it was nice while hard html and css thanks hehe.

---

<div class="post-metadata">

**Author:** ![erwblo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/erwblo/32/75_2.png) [@erwblo](https://community.glideapps.com/u/erwblo)\
**Post date:** [July 6, 2022, 11:35am UTC](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931/41 "2022-07-06T11:35:49Z")

</div>

Since Glide focuses mainly on internal functional tools, it won’t be much of a problem that they look a bit the same. For every company internal they are unique. More and better design tools would be nice though.

[Previous page](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931.md?page=1)

[Next page](https://community.glideapps.com/t/unsupported-html-css-in-the-rich-text-component-will-completely-break-in-the-coming-weeks/43931.md?page=3)
