# Uibuilder with Android System WebView

**URL:** <https://discourse.nodered.org/t/uibuilder-with-android-system-webview/75901>\
**Category:** General\
**Tags:** uibuilder\
**Created:** [1 March 2023 01:32 UTC](https://discourse.nodered.org/t/uibuilder-with-android-system-webview/75901 "2023-03-01T01:32:35Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 March 2023 10:35 UTC](https://discourse.nodered.org/t/uibuilder-with-android-system-webview/75901/21 "2023-03-06T10:35:26Z")

</div>

> [@Sean-McG](#):
>
> Everything is fine using chrome, so I guess its a webview issue ?

I've not much experience with webview - but my suspicions are that it is more likely the way that the wallpanel app is handling the webview. That is indicated by the type of issues being raised against it on GitHub. Also by the fact that it is working mostly OK for me after those initial oddities.

But then webview is designed really to handle internal app resources rather than external ones.

I think that if you wish to continue using wallpanel instead of one of the other kiosk type apps, you will need to raise an issue on GitHub.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 March 2023 10:36 UTC](https://discourse.nodered.org/t/uibuilder-with-android-system-webview/75901/22 "2023-03-20T10:36:13Z")

</div>

Closed on 20 March 2023 10:36 UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/uibuilder-with-android-system-webview/75901.md?page=1)
