Issue with Chrome Window and Window Dragging Behavior

Extra Black Bar and Misalignment of Mouse Actions

from Stardock Forums

Hello Groupy Community,

I've been experiencing an annoying issue while usiig Chrome with Groupy. Sometimes, when I drag a Chrome window, an extra black bar appears at the top. While this is tolerable, the problem worsens as the mouse behavior shifts upwards by about 5 cm. This makes it virtually impossible to interact with the window, and the only way to fix it is by closing the window.

Has anyone else experienced this issue? If so, were you able to find a solution?

groupy
5,050 views 3 replies
Reply #2 from Stardock Forums Top

There is an underlying bug in the chromium framework where the input processing gets disconnected from the rendering.  Exactly what triggers this is unknown.  It also impacts the electron framework apps like Discord which also use chromium as a base.

Offworld Trading Company
Reply #3 from Stardock Forums Top
Quoting basj, reply 1

Hello,
Sorry to hear you are having issues. Need more information on your system. Please refer here: https://support.stardock.com/space/SHC/1387954187/Contacting+Stardock+About+Groupy+Issues

Thanks
Basj,
Stardock Community Assistant.

End of basj's quote

Hello Basj,

Thank you for pointing me to the support page. I will gather the system information as suggested and submit it for further analysis. Hopefully, this will aid in identifying the root cause of the issue I'm facing with Groupy and Chrome.
Best regards

Quoting Neil, reply 2

There is an underlying bug in the chromium framework where the input processing gets disconnected from the rendering.  Exactly what triggers this is unknown.  It also impacts the electron framework apps like Discord which also use chromium as a base.

End of Neil's quote


Hi Neil,

Thank you for shedding light on this issue. It's interesting to note that this bug affects other applications based on the Chromium framework, like Discord. Knowing this could help in finding a more general fix for the problem. While it's frustrating that the exact trigger is unknown, your insight brings some relief in that this issue is not isolated to just my experience.

Best regards