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.