mattermost / mattermost/desktop
[Bug]: Mattermost window size are not restored on a high DPI secondary monitor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 980
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 30
Description
Checks before filing an issue
- This issue doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
- I have checked the issue tracker and have not found an issue that matches the one I'm filing.
- This issue is not a troubleshooting question. Troubleshooting questions go here: https://forum.mattermost.com/c/trouble-shoot/16.
- This issue is not a feature request. You can request features and make product suggestions here: https://mattermost.com/suggestions/.
- This issue reproduces on the most recent stable version, or the most recent prerelease version of the Mattermost Desktop App.
- I have read the contribution guidelines.
Mattermost Desktop Version
5.10.0
Operating System
Windows 10 x64
Mattermost Server Version
9.5.3
Steps to reproduce
My display configuration is as follows.
- The DPI of the primary monitor is 150%.
- The DPI of the secondary monitor is also 150%.
Terminate mattermost on the secondary monitor and start it again.
Then the window size will not be restored correctly.
Expected behavior
The window position and size are restored correctly.
Observed behavior
The position and size of the mattermost window on the primary monitor are restored correctly.
The position of the mattermost window on the secondary monitor is only restored correctly, and the size is restored to about 66% (≒(100÷150), which is smaller.
Log Output
[2024-11-18 09:45:04.722] [error] Logger Log level set to: info
[2024-11-18 09:45:04.969] [info] [App.Config] config.autostart has been configured: true
[2024-11-18 09:45:05.044] [info] [App.Config] config.autostart has been configured: true
[2024-11-18 09:45:05.241] [info] [ServerDropdownView] init
[2024-11-18 09:45:05.271] [info] [i18nManager] Set new language ja
[2024-11-18 09:45:05.294] [info] [App.Config] config.autostart has been configured: true
[2024-11-18 09:45:05.363] [info] [App.Config] config.autostart has been configured: true
[2024-11-18 09:45:05.658] [info] [App.Config] config.autostart has been configured: true
[2024-11-18 09:45:10.216] [info] [UpdateManager] Checking for update
[2024-11-18 09:45:10.443] [info] [UpdateManager] Update for version 5.10.0 is not available (latest version: 5.10.0, downgrade is disallowed).
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with Mattermost Desktop 5.10.0 on Windows 10 x64, using primary and secondary monitors set to 150% DPI. Investigate the window position and size restoration path for secondary monitors. Done means the window returns to its previous position and size after the app is terminated and restarted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100