{"action":"opened","issue":{"url":"https://api.github.com/repos/chrmarti/testissues/issues/14042","repository_url":"https://api.github.com/repos/chrmarti/testissues","labels_url":"https://api.github.com/repos/chrmarti/testissues/issues/14042/labels{/name}","comments_url":"https://api.github.com/repos/chrmarti/testissues/issues/14042/comments","events_url":"https://api.github.com/repos/chrmarti/testissues/issues/14042/events","html_url":"https://github.com/chrmarti/testissues/issues/14042","id":297311621,"number":14042,"title":"[hidpi] Scaling is not recomputed when changing between high/regular-DPI monitors (chromium behaves correctly)","user":{"login":"vscodebot[bot]","id":28792856,"avatar_url":"https://avatars2.githubusercontent.com/in/2406?v=4","gravatar_id":"","url":"https://api.github.com/users/vscodebot%5Bbot%5D","html_url":"https://github.com/apps/vscodebot","followers_url":"https://api.github.com/users/vscodebot%5Bbot%5D/followers","following_url":"https://api.github.com/users/vscodebot%5Bbot%5D/following{/other_user}","gists_url":"https://api.github.com/users/vscodebot%5Bbot%5D/gists{/gist_id}","starred_url":"https://api.github.com/users/vscodebot%5Bbot%5D/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vscodebot%5Bbot%5D/subscriptions","organizations_url":"https://api.github.com/users/vscodebot%5Bbot%5D/orgs","repos_url":"https://api.github.com/users/vscodebot%5Bbot%5D/repos","events_url":"https://api.github.com/users/vscodebot%5Bbot%5D/events{/privacy}","received_events_url":"https://api.github.com/users/vscodebot%5Bbot%5D/received_events","type":"Bot","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-15T02:24:55Z","updated_at":"2018-02-15T02:24:55Z","closed_at":null,"author_association":"NONE","body":"<!-- Do you have a question? Please ask it on https://stackoverflow.com/questions/tagged/vscode. -->\r\n\r\n<!-- Use Help > Report Issue to prefill these. -->\r\n- VSCode Version:\r\n```\r\nVersion 1.21.0-insider\r\nCommit 9a4ba7d06157091c882a03f118793db5d4657a82\r\nDate 2018-02-12T06:16:15.252Z\r\nShell 1.7.9\r\nRenderer 58.0.3029.110\r\nNode 7.9.0\r\nArchitecture x64\r\n```\r\n- OS Version: Linux 4.15\r\n\r\nSteps to Reproduce:\r\n\r\n1. Run Visual Studio Code - Insiders on a machine with a high dpi screen.\r\n2. Return home, dock your machine in a configuration with a single regular dpi screen.\r\n\r\nNote:\r\n\r\n1. `google-chrome-unstable` properly resizes itself to normal scaling.\r\n2. `code-insiders` stays doubled, and is unusable.\r\n\r\nNote, this also affects VSC when running in mixed DPI modes, but Chrome also doesn't handle this perfectly. Chrome will use the scaling of the primary monitor. For this exact bug, I'm only worried about moving between docked/undocked. It's a pain to have to restart VSC when everything else just works.\r\n\r\nScreenshot of VSC being improperly still scaled at 2x:\r\n![screenshot from 2018-02-14 18-23-09](https://user-images.githubusercontent.com/327028/36237952-297c92d6-11b4-11e8-8f05-df39486dd85a.png)\r\n\r\nScreenshot of Google Chrome dev edition properly scaled at 1x (w/o restart):\r\n![screenshot from 2018-02-14 18-23-18](https://user-images.githubusercontent.com/327028/36237953-29939558-11b4-11e8-8db7-41ad973a0f67.png)"}}
{"actor":{"display_login":"vscodebot"}}