# ⭕️ 2. Enhance native form: Prevent submission based on emptiness

**URL:** https://community.glideapps.com/t/2-enhance-native-form-prevent-submission-based-on-emptiness/74520
**Category:** Community Resources
**Tags:** custom-css, custom-code
**Created:** [July 1, 2024, 12:24pm UTC](https://community.glideapps.com/t/2-enhance-native-form-prevent-submission-based-on-emptiness/74520 "2024-07-01T12:24:21Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)
#### Post date: [July 15, 2024, 4:43am UTC](https://community.glideapps.com/t/2-enhance-native-form-prevent-submission-based-on-emptiness/74520/6 "2024-07-15T04:43:43Z")

</div>

If I understand you correctly, it seems that the component also does not leave a trace in the devtools. Are you suggesting displaying it with another component? Perhaps a method like this can be used: [In-app filter message for no matching results](https://community.glideapps.com/t/in-app-filter-message-for-no-matching-results/74679/7)? In other words, if this choice component is not found `(:not(:has(thisComponent)))`, then another choice component appears. However, can’t this be done without CSS?

---

_[View the full topic](https://community.glideapps.com/t/2-enhance-native-form-prevent-submission-based-on-emptiness/74520)._