[Bug] After Chrome version bump to 113 with WebGPU support, vtk.js render edge error

[supriome]

Bug description

vtk.js support webgpu if browser support webgpu, and when chrome v113 start support WebGPU by default, vtk.js render edge with some problem, you can see the line was been broken, and you can't change different render mode, if you switch mode Surface with Surface with Edge, you can't switch back. A error show Uncaught TypeError: Cannot read properties of null (reading 'getRenderable') because WebGPUActor.getRenderable() not exsit. Then your app is broken.

Steps to reproduce

Upgrade Chrome to version 113, and then go to the GeometryViewer example.

Detailed Behavior

No response

Expected Behavior

You can manually choose whether to support WebGPU feature.

Environment

• vtk.js version: 27.4.1
• Browsers: Chrome v113
• OS: MacOS and Windows

[supriome]

I notice that you can manually set viewAPI to 'WebGL' by renderWindow.setDefaultViewAPI('WebGL'), and I try this in my local machine by running GeometryViewer example, it's true that now I use WebGL Renderwindow, but the edge still show with error, it should be continuous straight line rather than dashed.

[floryst]

This is now fixed in v27.4.2 by defaulting to WebGL until the WebGPU implementation is stable. The fix will be backported shortly

[floryst]

Actually, I'll leave this issue open until the backport is complete.

[mengxiao-ac]

In our actual application development, we found an error when upgrading Google Chrome to version 113. We hope the development team can pay attention to this issue.

[floryst]

What version of vtk.js are you using? Right now, versions v19.x.x-v27.x.x all have new patch releases that fix this issue. All you will need to do is either bump the patch version for vtk.js and then re-run npm install.

…

On May 11, 2023 2:43:23 AM UTC, mengxiao ***@***.***> wrote: In our actual application development, we found an error when upgrading Google Chrome to version 113. We hope the development team can pay attention to this issue.  -- Reply to this email directly or view it on GitHub: #2819 (comment) You are receiving this because you modified the open/close state. Message ID: ***@***.***>

[floryst]

Closing as completed.