As the title says, the AbstractFrame.ready() method does not behave the way it’s documentation says.
Called by the framework after the screen is fully initialized and opened.
Override this method and put custom initialization logic here.
Let’s consider the following scenario:
- Window1 opens Window2 with:
openWindow("Window2", .THIS_TAB, someParams);
- Window2 opens in it’s
ready()function Window3 with:
openWindow("Window3", .NEW_TAB, someOtherParams);
- Window3 is a heavier window, so it takes aprox. 10 seconds to open.
Expected behaviour: Window1 opens Window2 in the same tab, then, with Window2 viewable, Window2 opens Window3 in new tab.
Actual behaviour: Window1 stalls untill Window2 AND Window3 are completely rendered then opens Window2 in the current tab and Window3 in a new tab at the same time.
Am I missing something, or this is the intended behaviour? I am using VAADIN engine for front-end rendering. And all the openWindow commands are executed from AbstractWindow sons’ controller.
If needed I will provide more context to my question as to why I need
ready() to behave EXACTLY as the docs say.