# Profanity filter **URL:** https://community.glideapps.com/t/profanity-filter/74483 **Category:** Ask for Help **Created:** [June 29, 2024, 10:27pm UTC](https://community.glideapps.com/t/profanity-filter/74483 "2024-06-29T22:27:23Z") **Posts on this page:** 1 **Showing post:** 4
### 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: [June 30, 2024, 11:35pm UTC](https://community.glideapps.com/t/profanity-filter/74483/4 "2024-06-30T23:35:12Z")
Preventing it to be created would be the most efficient in my opinion. > [@Exploring the Enhanced Capabilities of Glide's Native Form](https://community.glideapps.com/t/exploring-the-enhanced-capabilities-of-glides-native-form/69876/1): > > I want to share about the additional capabilities that we can achieve with Glide’s native form. What I have tested with the help of CSS is that native forms can also be applied for validation. Create your validation in the table columns and present it through messages via the “hint” component. Add the visibility conditional and the class “prevent-submit” to these hint components. Add the following CSS code: /\*Container Form\*/ #page-root:has(.prevent-submi… --- _[View the full topic](https://community.glideapps.com/t/profanity-filter/74483)._