I was wondering if there is a fix for this as the issues said below has since been closed but m now experiencing it in newer build
If you are experiencing this on a non-stable-release browser, then unfortunately - yes that is expected behavior. Supporting alpha/beta browsers is a difficult proposition although we are talking about it and feedback is welcome.
If you are experiencing this on a stable-release browser, then please submit a ticket to email@example.com and mention me.
Ok, thanks, I’ve contacted support now im also running Chrome on the stable channel so I assume that’s classed as “stable”?
We believe the current slate of alpha/canary/beta browsers should be working now as well