Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegram Desktop resets its position after switching to fullscreen #17

Open
alex-voodoo opened this issue Mar 3, 2021 · 1 comment
Open
Labels
bug Something isn't working

Comments

@alex-voodoo
Copy link

alex-voodoo commented Mar 3, 2021

This is probably connected to #12.

I'm on Fedora 33, using the latest version of UltrawideWindows (installed it via git clone).

I move the Telegram's window to some position using one of shortcuts exposed by UltrawideWindows. The window moves and stays there, switching the virtual desktop doesn't break anything. However, when I click on any image or video in any message within Telegram, it opens fullscreen, and when I close it to return back, the messenger's main window is reset to the position that has been set to it previously using the other means, not the UltrawideWindows script.

For example:

  1. I move the main Telegram window somewhere in the middle of the screen.
  2. I press Ctrl+Meta+Numpad6. The window moves to 1/4 width at the right side of the screen.
  3. I open some media. It opens fullscreen.
  4. I press Escape or click the Close button.
  5. The window position is reset to what it has been in (1).

The unwanted reset can be avoided if after (2) I alter the window position manually. Dragging the window border a few pixels here and there is enough.

I tried the same with other applications, e.g., Chrome and Firefox, they worked properly, resetting their position to what has been assigned via UltrawideWindows. Probably they use some other method of going fullscreen, or do a better job on restoring the position.

@lucmos lucmos added the bug Something isn't working label Mar 13, 2021
@lucmos
Copy link
Owner

lucmos commented Mar 13, 2021

Thanks for the bug report!

I'm also experiencing strange behaviors with some apps since I switched to a dual monitor setup.
I'm not sure if the problem is the dual-monitor or some update in kwin broke something.

I'll try to look into it, but I'm not very optimistic. I do not have much experience with KDE development

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants