# 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:** 2

<div class="post-metadata">

### Author: ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@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")

</div>

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

---

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