Sections containers visible during layout processing for action 'new'

[metas-mk]

Type of issue

Bug

Current behavior

When creating a new record in metasfresh, then an input field appears for a few milliseconds and disappears again after the layout is loaded.

Expected behavior

Don't show that input field.

Steps to reproduce

Happens in different windows with "new" action. But try to reproduce in window/143/new

[damianprzygodzki]

Cannot reproduce, even with throttling applied.

What i think it is a just primary element group container - not input.

What is the reason to do not show that?

EDIT: I see that it is regular way of rendering window - if it is slow it depends on your computer and one solution is to wait until the data comes, but not so long ago we had this conversation and you said to do not wait for data when rendering window - because we have layout already fetched.

[cadavre]

to do not wait for data when rendering window - because we have layout already fetched

This is valid statement when we have enough data to actually render the layout. Single primary section container doesn't look like rendered layout.

I can reproduce, one thing to say is that it didn't appear previously (2w ago) so something might have changed.

[damianprzygodzki]

@metas-mk @cadavre Could you provide environment, because for me it doesn't occur. The window is displayed immediately when ready.

Branch master, Chrome, OSX, disabled cache, /window/143/new, 1.5Mb/s.

And what is the expected behavior? To do not render anything before layout + data fetched?

[cadavre]

Only agreed solution is:

one solution is to wait until the data comes

[teosarca]

uber low prio :)