I have noticed a weird problem, at least in Chrome. It seems tables and grids, when you go from not full screen to full screen, or vice versa, the full screen is not sized correctly. I use MprTheme for a legacy theme. Below are the images in question.
I am tested one app, and I noticed that responsive width ranges are updated when I click. So the root cause could be the same despite in your case it is not about responsive.
One thing as a workaround you could try is to set browser window resize listener and do JavaScript call of “vaadin.forceLayout()” upon resize and see if it helps.
E.g. in MainLayout (Flow) the default Route, add
private Registration listener;
@Override
protected void onAttach(AttachEvent attachEvent) {
super.onAttach(attachEvent);
getUI().ifPresent(ui -> listener = ui.getPage().addBrowserWindowResizeListener(event -> {
ui.getPage().executeJavaScript("vaadin.forceLayout()");
}));
}
@Override
protected void onDetach(DetachEvent detachEvent) {
// It is needed to remove the BrowserWindowResizeListener during detach
// in order not to bloat browser resources
listener.remove();
super.onDetach(detachEvent);
}
I am tested one app, and I noticed that responsive width ranges are updated when I click. So the root cause could be the same despite in your case it is not about responsive.
One thing as a workaround you could try is to set browser window resize listener and do JavaScript call of “vaadin.forceLayout()” upon resize and see if it helps.
E.g. in MainLayout (Flow) the default Route, add
private Registration listener;
@Override
protected void onAttach(AttachEvent attachEvent) {
super.onAttach(attachEvent);
getUI().ifPresent(ui -> listener = ui.getPage().addBrowserWindowResizeListener(event -> {
ui.getPage().executeJavaScript("vaadin.forceLayout()");
}));
}
@Override
protected void onDetach(DetachEvent detachEvent) {
// It is needed to remove the BrowserWindowResizeListener during detach
// in order not to bloat browser resources
listener.remove();
super.onDetach(detachEvent);
}
Tatu, this seems like the same answer from 3 months ago. Is it, or maybe you posted the answer to the wrong question? Just confirming I am not missing something.