Mojtaba Samimi
Mojtaba Samimi
I'm looking forward to @alexcjohnson's review on this as well. Also thanks to @marthacryan and @birkskyum reviews & contributions :pray: This PR helps unblock `Chart2Music keyboard and sound accessibility features`...
Thanks for the reviews! Before merging this PR, I'd like to do additional QA on the python side on loading the bundle.
`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`
Keeping an eye on https://issues.chromium.org/issues?q=componentid:1456284.
`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`
I could confirm that e.g. [this parcoords graph](https://codepen.io/MojtabaSamimi/pen/oNryozX?editors=0010) is not rendering on Chrome 128 as well as Edge 128.
`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`
Other applications also encountered this: https://community.esri.com/t5/arcgis-online-questions/map-error-in-new-chrome-update-128-0-6613-85/td-p/1525829
`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`
FYI `chromium.org` considered this regression and labeled it as P1. See https://issues.chromium.org/issues/361823993.
`Chrome 128` seems to have problem rendering WebGL traces including `parcoords`, `mesh3d`, `surface`
The regression is now fixed by Chromium 128.0.6613.113 https://chromium.googlesource.com/chromium/src/+/refs/tags/128.0.6613.113 Please consider updating your browser if you encountered this bug. Closing.
> It doesn't look like these deprecations will appear in the console if these traces are used... is that correct? I would expect a console warning A warning is now...
@emilykl Can I have your review on this PR please?
@ndrezn Would you please take over this PR?