autoSize on Window not properly working - different size and overlapping texts

[SimonF]

Hi there,
When the user has logged in for the first time, we show a window with the version highlights.
Every-time we are releasing a new version we are also using a new smartclient-version to get rid of bugs.
For a new version we are creation a cloudfront-distribution with the smartclient files.

So when logging in the smartclient-files cannot be in the in the cache. (This can be reproduced with a CTRL+F5 click)
After pressing F5 the window, does get the correct size of the window.
All this was reproduced with the latest downloadable version (SmartClient_v111p_2017-10-25_Pro).
This is reproducable with the latest Firefox Version (56.0.1 (64-Bit))


We have learned from the previous bugs, that we cannot ignore bugs in a beta version (https://forums.smartclient.com/forum...-latest-chrome)
So it is even worse in the newest firefox beta 57.0b11 (64-Bit)

The correct size is after the F5 click.

Canvas.resizeControls(4);Canvas.resizeFonts(2);
isc.Window.create({
    "ID": "window",
    "width": 550,
    "title": "test window",
    "autoSize": true,
    "autoCenter": true,
    "items":
    [isc.VLayout.create({
            "ID": "rootLayout",
            "width": "100%",
            "height": "100%",
            "members":
            [isc.Canvas.create({
                    "ID": "textCanvas",
                    "width": "100%",
                    "height": "100%",
                    "contents": "Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad minim veniam, quis nostrud exerci tation ullamcorper suscipit lobortis nisl ut aliquip ex ea commodo consequat. Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore te feugait nulla facilisi. Nam liber tempor cum soluta nobis eleifend option congue nihil imperdiet doming id quod mazim placerat facer possim assum.",
                }),
                isc.DynamicForm.create({
                    "ID": "form",
                    "width": "100%",
                    "fields":
                    [{
                            "ID": "checkboxItem",
                            "name": "checkboxItem",
                            "title": "example",
                            "type": "boolean",
                        }
                    ]
                })
            ]
        })
    ]
});

Best regards

[Isomorphic]

Could you clarify what you're reporting here - a bug in the latest Firefox version, not reproducible in older versions of Firefox?

Further, are you able to reproduce this in the standard SDK environment, or only when using your CDN deployment?

Note that as far as the bug from that other thread, it appeared in Chrome 61 and appears to be resolved in Chrome 62. So it's a little unclear what to do when rapidly updating browsers break something so fundamental - the set of workarounds required can easily break other functionality.

[SimonF]

Okay, I make a distinction between two bugs
1. Firefox (latest version 56.0.1 (64-Bit)) does have visible issue with the latest downloadable Version (now SmartClient_v111p_2017-10-26_Pro).
When loading the example above (in #1) with CTRL+F5 it looks like this:

After that if you are clicking again F5 it looks like this


It is reproducable with a normal local setup.

2. Opening the same example as shown in #3 in the latest Firefox beta, the checkbox is displayed in the text like this:

We don't know if this is a bug in firefox or in smartclient. How are we supposed to know the difference?
It's just a heads up. Thinking back to the Chrome-Bug it seems no one has tested any beta-build. We have seen the bug in the beta build, but we have though this will be fixed either from smartclient or from google chrome. None of it was the case, so instead of not making any mention of it, we considered for posting it as we have found it.

Kind regards

[Isomorphic]

This will be fixed for SGWT 6.1p/SC 11.p and newer releases in tomorow's nightly builds, dated 2017-11-04.

Note that by default, if font loading takes a long time, such as would be expected upon the initial load with an empty cache, the FontLoader may need to trigger the redrawing of several widgets to account for size changes. If you'd rather just wait until the fonts are loaded before starting to draw, you could configure drawing to start upon receiving the "fontsloaded" Page Event