We are experiencing the same issue. Turning on ‘hardware acceleration’ in chrome did help. The customer is running chrome 117.0.5938.150 (64-bit). We are using jqwidgets 16.0.0. Is there a way to capture chrome logs for this behavior?
