hterm: moving window between displays of different DPIs results in incorrect scaling |
|
Issue descriptionGoogle Chrome 65.0.3299.0 (Official Build) canary (64-bit) Revision 0 Platform 10232.0.0 (Official Build) canary-channel eve-kvm What steps will reproduce the problem? (1) Attach an external monitor of different DPI (2) Open an hterm window and fill the terminal with lines of text (3) Move the window from one monitor to the other (4) Note that hterm notices the resize (it displays the updated geometry), but the bottom lines may be cut off (5) Hit ctrl-0, which should be a no-op (6) Scaling is fixed so that the bottom lines are no longer cut off (7) Repeat 3-6 back to the original monitor. What is the expected result? Step 5 shouldn't be necessary. What happens instead? Lines get cut off, and you have to hit ctrl-0 to fix things.
,
Jan 16 2018
Hook on newline, but limit to checking once every n seconds? Regardless, resize is *not* calculating things correctly, or it's using (or being fed) a stale value of DPI or something. I can move the window to the other display, and then resize the window and it still has the wrong DPI. Ctrl-0 is the only way I've found to fix things.
,
Jun 8 2018
not a fan of any timer based approach googling around, there might be a way to use the scroll event to detect when the font changes. i'll have to try it on attached displays to see if it helps. the algo is covered here: https://github.com/marcj/css-element-queries/blob/master/src/ResizeSensor.js |
|
►
Sign in to add a comment |
|
Comment 1 by vapier@chromium.org
, Jan 16 2018