Windows 11, Latest Chrome, Kiri in Onshape
Hi all. Anyone got a workaround for Animation not working? This has happened before, it pops up with the security context message.
many thanks in advance
Inside Onshape? If so, it’s related to this issue. There is no good workaround at this time except to run Kiri on Grid.Space or use the desktop binaries. But the issue documents the cause, if you want to understand it.
Having said that, I am working on a pop-out animate window. This would bring the animation context outside of Onshape’s iframe security context which would allow high performance features. It’s not a simple task and requires significant changes to the way Kiri stores data … which was already on the todo list for the next major release.
Thank you Stewart. That makes a lot of sense as it works fine outside Onshape.
Many thanks again and thank you for such a great solution.
1 Like
Hi Stewart,
Do you have a ticket with Onshape or such that we millions of KM users can +1 for them?
After exploring this issue in depth, I do not think Onshape has a good set of options to choose from. Current web security standards do not allow them discretely trust one iframe without extending that same trust to all other elements on the page. And that would mean any 3rd party script could be compromised and used to exploit their platform.
I was able to work around this due to Chrome’s Origin Trials which allowed me to re-enable SharedArrayBuffer without touching anything else. That ended (after a multi-year run), and there is no alternative or equivalent.
I’ve been testing a pop-out animation window that seems to work. When Kiri is in Onshape in CAM mode, selecting animation bundles the path data and sends it to another tab to be rendered. This allows us to escape iframe origin security.
With a little luck, it’ll be in production later this weekend.
fun little side note. I built an Electron wrapper around Onshape using the same desktop build pattern for the Kiri:Moto executables. This allows me fine granular control over security which typical browsers prevent. It also allows Onshape to show up as a separate process from the browser meaning I can hide / minimize / tab it and see it as a separate icon. And, of course, it lifts all of the restrictions I’m having issues with right now.
2 Likes
:-/
I suppose the point of a ‘trial’ would be that they (Chrome people) have already received and considered feedback.
Appreciate your effort to find a way to get the animation done.
Area Surface ops also fail on undefined SharedArrayBuffer. Same issue? I’m guessing that’s harder to hand off to another tab.
That sounds … interesting.
I know nothing about Electron. Is that a thing that can be done without a web dev environment?
That sounds like a method that could generalize broadly for lots of things.
Ah, yes. This is a performance optimization to share memory with the GPU. There may be a workaround by falling back to less performance ArrayBuffers. I will investigate.
yes, also on my back burner. super useful in theory. quickly devolves into developing your own browser on top of Chromium.