i had to use the occlusion flag so chrome would respond, but new chrome has
no flag.
I found a user post that by adding -disable-backgrounding-occluded-windows
to the chrome startup it fixes it again.
Is there some way for virtuawin to solve this? Mainly because I use pgadmin
which has chromium in it, and I have no fixing flag for that.
i had to use the occlusion flag so chrome would respond, but new chrome
has no flag.
I found a user post that by
adding -disable-backgrounding-occluded-windows to the chrome startup it
fixes it again.
Is there some way for virtuawin to solve this? Mainly because I use
pgadmin which has chromium in it, and I have no fixing flag for that.
i had to use the occlusion flag so chrome would respond, but new chrome has
no flag.
I found a user post that by adding -disable-backgrounding-occluded-windows
to the chrome startup it fixes it again.
Is there some way for virtuawin to solve this? Mainly because I use pgadmin
which has chromium in it, and I have no fixing flag for that.
I actually found -disable-backgrounding-occluded-windows can be used on
the shortcut, hopefully this will remain!
On Thu, Jan 6, 2022 at 1:41 PM Rick LaBanca rick@ricklabanca.com wrote: