Input and output disappearing after changing window size of browser

[SergioGzzBrz]

When the problem occurs
Whenever the size of the window is small enough, the ide shows a menu at the bottom of the different tabs (code, input/output, and users).
But after you return to full screen, it now only shows the tab that was active in the menu. For example, if you had a smaller window with the code tab open, and you return to fullscreen, now the input/output section cannot be seen. I added an image for this case, and how it can happen for the other tabs too.

I've tried in edge and chrome, and occurs in both browsers.

Temporal solution
Reloading the page is the only method I've found that solves this problem, until the window is made small again.
Also, I just found out that clicking the "1 user online" button also fixes it.

Images

Normal window:

Making the window smaller, showing the menu

Image input/output not appearing after maximizing the window

Image of code not appearing if last active tab in the menu was code:

Image of neither appearing if last active tab was users:

[bqi343]

hm, I'm on chrome and I can't reproduce this. @thecodingwizard any clue?

[thecodingwizard]

Hmm, I also can't reproduce this. @SergioGzzBrz are you running on Windows 11? Could you also check the developer tools console to see if there are any error messages?

Also, are you entering full screen by clicking some full screen button? What happens if you try resizing the window by dragging the window borders rather than clicking the full screen / maximize button?

[SergioGzzBrz]

Yes, I'm on Windows 11. And resizing the window by dragging it does not cause this error to appear, it only happens when clicking on the maximize button.

In the developer tools there are just warnings that do not change whenever the issue appears. Here are the specific warnings (on edge):

[thecodingwizard]

If I had to guess, it's probably something related to https://stackoverflow.com/questions/49039102/window-resize-or-window-onresize-not-firing-when-the-window-is-maxim (ie. we can try adding a short settimeout after window resize event or something). Unfortunately I don't have a windows machine to test this :(