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

Well, this would certainly bring a sigh of relief to most of us. If it’s a matter of reimplementing the CSS in a different manner, then no problem!


strongly agree!



This gives me hope that my Roster Calendar may continue to work. I barely slept last night trying to figure out what I was going to do about that :cry:




1 Like

I think it’s useful to understand Glide’s mission. If one truly adheres to Glide’s mission, then in my opinion one cannot support css (and markup for that matter) being a necessity in Glide. Optional, why not. Necessary, no.

Layout structure, not esthetics
Bob mostly uses css to compensate for placement/structural limitations in the builder, and I think this makes good sense. So Glide could probably add a few placement/structural features in the builder. But I wouldn’t push it with colors. Most 1 billion creators couldn’t design a good looking app if their life depended on it: giving Glide builders too many design options would just about guarantee that the output would look terrible.

Bob’s list

Losing business / We depend on css+html for customer success

“Because of some sort of design limitation.”
Well, don’t oversell Glide’s capabilities: css isn’t and never has been part of the package. It’s pretty simple.

“Because Glide projects look the same.”
Be unique with the specific business pain point you solve internally within a business. If that problem repeats across businesses, then sell the same solution. But being unique in how the app looks is not that important in B2B (with Glide you won’t be building the next TikTok). This is especially true for apps for work (business), apps for good (non-profit) and apps for fun (personal).

CSS in Glide Pages
As it’s already been announced publicly, CSS might be optional in Pages at some point, just like in any website builder. But let’s be honest, 99.99% of Glide builders would probably be better off staying away from it.

If I had to guess, a design-related and possibly component-related announcement is just around the corner. The Glide team usually makes minor enhancements here and there, is pretty quiet for a few weeks and then suddenly releases something huge on the product side: 30+ computed columns, Glide Tables, Glides Pages, external data sources come to mind. Well, I feel Glide has been a little quiet these days, and now suddenly there’s a lot of talk about layout (css and design). This could only be related to the new computational model for Apps, but I think something else is brewing. Of course I have no idea and could be totally wrong.


your remarks are totally wrong… Glide is big mostly because of the best way of handling google sheets and the flexibility of applying CSS if there are limitations… if Glide decides to go its own way at this point… it will be a total failure… but lots of work for me to get all these big accounts into Google Apps… but, I always will feel bad for the little ones who lost months of work.
and I already announced to all my customers that I will be charging for fixing CSS… is not my fault… all of them agree… many of them wanna switch to another solution (they expect stability)… so… is gonna be a busy few months… like when Glide changed plans… :wink:


On the other hand, this is the risk and the consequence of using startup tools. You join them when they are still searching and changing all the time. The business models, the target audiences, the functionalities, the technique. Part of startup life, I’m afraid, has been my experience in using maybe a hundred of them in the last decade.


Well the Glide Team have always said that CSS manipulation techniques may break one day. For this reason we have generally tried to avoid them wherever possible.

It’s therefore difficult to complain, on the assumption that a reasonable timeframe is given for us to address issues with existing solutions that do use them.

I would like to understand:

  • What is the actual timeframe for switchover
  • Will existing apps be unaffected or do all apps need to move to NCM
  • Is any more UI flexibility available once the transition is complete

The last point is important since even the target audience of “internal apps and their customers” generally want more UI customisation than Glide currently allows.


Same here! I think there is a lot that can still be simpler.

@Darren_Murphy ow is the day going? CSS/html-style usage has A New Hope ™ :joy:

Question for you and @ThinhDinh - I use this bit of code in a number of places to provide an alternative to the standard “See All”. Do you think it will still be usable based on your insights?

Funny - I literally know nothing about CSS/HTML (did I mention I spent 30 years in sales!) but have successfully integrated it in a number of places to add key functionality within Glide because this team of experts have been so articulate in its usage and deployment.

ALSO - as I have new questions about CSS should they go into a new thread versus pilling-on to this one?


→ View As Agenda

.see-all-custom {
font-weight: 600;
font-size: 0.875rem;
line-height: 1.0625rem;
color: #4574E8;
position: relative;
float: right;

I think you can expect this piece of code to break, yes.

We could keep this thread to comments about David’s initial post: “Unsupported HTML/CSS in the Rich Text component will completely break in the coming weeks”. You can always create new topics about CSS and give them a descriptive title, it helps keep the forum as organized as possible :slight_smile:

Please let us know exactly when things will break so we can be ready to fix the affected apps. Thanks! :pray:

OMG :cry:

Oh thanks!! what good news you have given me David

Simple homage to the HTMLs and CSSs once used :pensive:


Aww, Lucas! Big bear hug from BERlin :bear::people_hugging:

1 Like

Lol :cry:

If it’s just a change in the DOM structure as David and Mark said yesterday, then that won’t break, since it’s styling based on a custom component not related to the DOM, as I understand.

Gotta say it’s best to wait on how the DOM will actually look like and then make changes based on that.

Same to the comment @Pablo_Reyna replied to, and @kabookie asked me earlier.


@david Could we be able to use it in Pro Plan or +?