Funky resizing issues

[Stanzilla]

• I am on the latest Hyper.app version
• I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Windows 10 1709
• Hyper.app version: 2.1.0
• Link of a Gist with the contents of your .hyper.js: https://gist.github.com/Stanzilla/e8ef5c460bbeb8b61699db1518ee7a5a
• Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere):
• The issue is reproducible in vanilla Hyper.app:

Issue

Various display bugs happening when resizing the terminal with multiple tabs open, happening on 2.1.0

https://dl.dropboxusercontent.com/s/gmlpceuwd2i1byw/2017-11-03_22-34-18.webm

It works fine in 1.4.8 so it is a regression.

[jaller94]

This is not limited to Windows. I am also affected on MacOS 10.13.

[NicholasJohn16]

I just reinstalled Hyper 1.4.8 on Windows 10 and I'm having this same issue. Even happens when you have panes and you resize the window.

[Stanzilla]

I just tried on 1.4.8 yesterday and could not repro, weird.

[jaller94]

In 2.1.0 it doesn't affect my first tab of a window.

1. Open Hyper.
2. history (a program with output)
3. Open another tab.
4. history
5. Resize the window.
6. Switch to the first tab. All looks good.
7. Resize the window.
8. Switch to the second tab. The output of the history command can be seen, however, with only one character per line.

[NomNuggetNom]

Also suffering from this issue and I can reproduce every time. I'm on 2.1.1.

[NomNuggetNom]

Bump on this. Makes the terminal unusable. Any more info needed?

[jaller94]

I wouldn't say unusable. Since the pre-releases are out I'm only using those because of the performance gain. However, I am affected of the resize bug roughly every 10 minutes. To me it seems like the size indicator at the bottom right iterates quickly through all tabs. When changing the size by one unit, I multiple values show up sequentially. Some of them being the actual size like "64x32" and others being "1x1". That's when I know some tab(s) have been squeezed.

[dfenster]

I also have this problem

[LabhanshAgrawal]

@Stanzilla I guess we should close this issue as it was for v2 and I don't think it's present in canary now.