Yes, that’s the core of the problem.
A WebViewer placed directly on the screen cannot size itself correctly. It has no proper boundaries, which is why you see the dead space. (You can see this for yourself by using the Webviewer Computed Height blocks - it will return ‘0’ every time.)
The fix is to nest it properly and then let a container control its visible size.
Here is the setup that works reliably:
-
Put a Layout at x = 0, y = 0
-
Put a Container inside that Layout
-
Put the WebViewer inside the Container
Next, you need to make sure the layout itself is the exact height of the device. I recently posted a working solution for that here:
https://community.thunkable.com/t/solved-how-to-make-android-layouts-fit-correctly-on-every-device/4108120
Once the layout has calibrated and is the correct height:
- Set the WebViewer height and width larger than its parent container
For example:
-
WebViewer height = Layout height × 1.3
-
WebViewer width = Layout width × 1.2
This sounds entirely stupid (and it is) but it works because the container acts as guard rails and clips it to the exact screen size.
So instead of trying to make the WebViewer fit, you oversize it and let the container adjust the size..
If everything is nested correctly, the WebViewer will now fill the screen perfectly on all devices.