10-12-2025, 01:18 AM
(This post was last modified: 10-12-2025, 01:18 AM by Alexandre Machado.)
We have found and fixed the issue.
The behavior of mobile Chrome browsers have changed recently (not exactly sure when, though).
The thing is that Chrome will report wrong sizes (CSS sizes, not pixel sizes) of the page when IW starts, unless a viewport tag is provided. Firefox does it "right" and report the correct sizes regardless of the viewport tag. This causes IW to start the application with wrong form sizes, causing the effect that you mentioned.
You can force it to behave correctly using this viewport tag in your ServerController.MobileOptions.ViewportTag:
<meta name="viewport" content="width=device-width, initial-scale=1.0">
This fixes it.
Anyway, we are releasing a new update which will force the correct viewport tag regardless of your ServerController settings.
Cheers,
The behavior of mobile Chrome browsers have changed recently (not exactly sure when, though).
The thing is that Chrome will report wrong sizes (CSS sizes, not pixel sizes) of the page when IW starts, unless a viewport tag is provided. Firefox does it "right" and report the correct sizes regardless of the viewport tag. This causes IW to start the application with wrong form sizes, causing the effect that you mentioned.
You can force it to behave correctly using this viewport tag in your ServerController.MobileOptions.ViewportTag:
<meta name="viewport" content="width=device-width, initial-scale=1.0">
This fixes it.
Anyway, we are releasing a new update which will force the correct viewport tag regardless of your ServerController settings.
Cheers,