# WebView component: visibility condition

**URL:** <https://community.glideapps.com/t/webview-component-visibility-condition/16410>\
**Category:** Feature Requests\
**Created:** [September 27, 2020, 9:34am UTC](https://community.glideapps.com/t/webview-component-visibility-condition/16410 "2020-09-27T09:34:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AyS\_0908](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ays_0908/32/27349_2.png) [@AyS\_0908](https://community.glideapps.com/u/AyS_0908)\
**Post date:** [September 27, 2020, 9:34am UTC](https://community.glideapps.com/t/webview-component-visibility-condition/16410/1 "2020-09-27T09:34:58Z")

</div>

Hi @mark, when we collect ‘www’ from users (for ex. in a form), we cannot know upfront if it will be webview-able.  
When it is not, there is a ‘not at all UX-oriented’ grey screen appearing.  
Therefore, it’s often better to just get rid of the WebView component and let only the WebLink one.

=\> An alternative would be a dedicated visibility condition on the WebView enabling us to let both components:

- if ‘embedding’ connects to the www \> display WebView result,
- if not, hide WebView component.  
nb: this could also be the standard operating model for this component (ie. on Glide side) without having us to set-up the visibility.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/c/cae5cf8d2361463e8ce55b2e1fb972d6ee7d4575.png)