Can't drag a tab out into it's own window. Get a blank white screen.

Can't drag a tab out into it's own window. Get a blank white screen.

avatar

Howdy,

Running 13.0.17.0 and noticed that if I try to drag a tab from the main bar out so that session is in its own window, I end up with a blank white screen and can't access that tab at all. If I just drag it out a bit so it's floating, it works OK. If I drag it out and anchor it to the top of the screen so it goes fullscreen, that's when I get the blank white window.

I had to completely kill the program and open it back up and reconnect to the server to get back in it. I had someone else verify it on their machine and they have the exact same problem.

Thanks.

All Comments (9)

avatar

I will ask the QA to reproduce it.

Regards

David Hervieux

avatar

Hello,

What type of session are you trying to undock ?

Best regards,

Alexandre Roy

avatar

Just a regular old RDP session. Grab a tab, drag it up to the top edge of the screen, and let go. Gives me a blank white screen. I'm on 13.0.19.0.

avatar

Hi,

Could it be possible for you to export this session without the credentials and the hostname and email it to aroy@devolutions.net?

I'm particularly interested by the display settings.

Thanks.

Best regards,

Alexandre Roy

avatar

Hello again,

Discard what I've asked in the last post from you. I actually was able to reproduce the issue. It seems to only happen if you drag and drop it directly at the top of the screen. If I drag the window and release it in the middle of the screen then drag it on top it work perfectly. Thanks for reporting this. A ticket has been sent to the engineering team.

Best regards,

Alexandre Roy

avatar

We do have someone still on 12.9 and it doesn't happen to him so it seems to be just something within 13.x

avatar

Hello,

This issue has been fixed internally and should be available in the next release.

Thank you.

Best regards,

Alexandre Roy

avatar

Awesome! Thanks for the update.

avatar

Hi,


Sorry for the late response. This issue is fixed in the beta version 13.5.5.0.

Thanks for reporting this.

Best regards,

Alexandre Roy