# 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:** 14
**Page:** 1
### Author:  [@Hassan\_Nadeem](https://community.glideapps.com/u/Hassan_Nadeem)
#### Post date: [July 6, 2022, 9:27pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/1 "2022-07-06T21:27:05Z")
Hi Gliders,
On this thread we can make a list of all the simple yet important features that are achieved only by CSS, so maybe Glide can add them before imposing a ban on CSS.
My list is:
1. Colorful texts
2. Colorful buttons
3. More than 4 horizontal tiles on inline lists
You all can add yours as well
---
### Author:  [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)
#### Post date: [July 6, 2022, 9:48pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/2 "2022-07-06T21:48:58Z")
My top reasons for using CSS:
- hiding back button
- reconfiguring of inline list fields (especially the card layout)
- making components sticky to top/bottom of screen
- manipulating the comments component to provide a more chat-like experience
- making video component “inline” and not full width
- adding badge/counts on top of inline list tiles or tab icons
- creating a modal overlay on a screen that forces a user to click a button before viewing content on that screen
- more than 4 columns for inline list \> tiles
- choice component: scrolling chips (not stacked); making a choice component sticky so it can act like a screen filter
---
### Author:  [@Yasin\_Hassanien](https://community.glideapps.com/u/Yasin_Hassanien)
#### Post date: [July 6, 2022, 10:21pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/3 "2022-07-06T22:21:57Z")
Hiding back button is critical
---
### Author:  [@MattLB](https://community.glideapps.com/u/MattLB)
#### Post date: [July 6, 2022, 10:46pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/4 "2022-07-06T22:46:06Z")
And nice looking tables. This feature request seems to go back to at least Oct '20
It comes from this thread: [Expand 'Image' and 'Title' component to edge of screen - #30 by ThinhDinh](https://community.glideapps.com/t/expand-image-and-title-component-to-edge-of-screen/4296/30)
---
### Author:  [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)
#### Post date: [July 6, 2022, 11:41pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/5 "2022-07-06T23:41:12Z")
This list covers everything I’ve ever done with CSS.
---
### Author:  [@Uzo](https://community.glideapps.com/u/Uzo)
#### Post date: [July 7, 2022, 12:09am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/6 "2022-07-07T00:09:51Z")
- resizing and positioning elements (fixed, absolute, and relative)
- multiple column tables, as list
- visibility based on user screen size
- fonts color, size, and type for all elements
- changing components backgrounds, borders, shadowing
- on click and on hoover reactions
- arranging multiple components horizontally, for desktop view
---
### Author:  [@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")
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…
---
### Author:  [@resepsionis\_ganteng](https://community.glideapps.com/u/resepsionis_ganteng)
#### Post date: [July 7, 2022, 5:31am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/8 "2022-07-07T05:31:38Z")
Like renaming the target element?
---
### Author:  [@Manikandan\_R](https://community.glideapps.com/u/Manikandan_R)
#### Post date: [July 7, 2022, 7:06am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/9 "2022-07-07T07:06:18Z")
Altering the components size,button size to small,table size, provide colour change to all components,button bar progressing image like in button click.
---
### Author:  [@Xavier\_Delplanque](https://community.glideapps.com/u/Xavier_Delplanque)
#### Post date: [July 7, 2022, 8:44am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/10 "2022-07-07T08:44:41Z")
A few things I listed in the app made with @grumo
Some have already been mentioned.
I’m also adding a visual to clarify the end result.
- pin components (buttons, stopwatch, hint …) to the bottom of the screen
- a smaller / more configurable stopwatch
- allow to hide the tab navigation on specific / modal screens
- display rich text and image components as cards so it looks more tappable
---
### Author:  [@grumo](https://community.glideapps.com/u/grumo)
#### Post date: [July 7, 2022, 5:38pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/12 "2022-07-07T17:38:02Z")
We made such an awesome app for such a good cause! It will be sad to see some of the functionality die when CSS is removed. I really hope the Glide team come come up with some native alternatives. Please! 🙏
---
### Author:  [@saphier](https://community.glideapps.com/u/saphier)
#### Post date: [July 7, 2022, 6:51pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/13 "2022-07-07T18:51:23Z")
We use CSS to make our apps make better use of real estate on a desktop, and appear less like a phone app on a desktop. Example: this is a detailed view with an inline list and a single record view depending on the user selection with some CSS manipulation.
Given the existence of Pages I’m sure it’s not a use case that is of top priority. But it was certainly nice alternative for us specifically.
So my unlikely feature would be: improved layout options for desktop view in Apps 🙂
NB: My understanding is that CSS feature is not being disabled, just that the way we target elements may no longer work because the structure of the page will be changing in the next couple of weeks. So I’m hoping once the CSS structure settles down we’ll be able to re-create our existing views. But if they have dynamic class names that may not be possible.
---
### Author:  [@erwblo](https://community.glideapps.com/u/erwblo)
#### Post date: [July 7, 2022, 7:25pm UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/14 "2022-07-07T19:25:09Z")
Feels doable!
---
### Author:  [@Joe\_Gabriele](https://community.glideapps.com/u/Joe_Gabriele)
#### Post date: [September 8, 2022, 12:50am UTC](https://community.glideapps.com/t/list-of-all-features-needed-before-css-ban/43998/15 "2022-09-08T00:50:59Z")
Looking to see if anybody has some CSS ideas on how to reformat progress bars from
To something more like this:
Main parts being moving the bottom text to the right side of the bar as I figured out how to shorten the width of the bars adjusting the margin.
Thanks!