You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Figma uses WASM + QuickJS for running plugin code. We already use QuickJS in NEAR for JS smart contract execution. Is there any way we can leverage WASM + QuickJS for component security?
At the moment there is no DOM access in WASM, but there are proposals in progress to move towards support for that. Once that support is added, will WASM still be effectively isolated? Or is it only isolated because the attack vectors haven't been enabled yet?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Figma uses WASM + QuickJS for running plugin code. We already use QuickJS in NEAR for JS smart contract execution. Is there any way we can leverage WASM + QuickJS for component security?
context: https://www.figma.com/blog/an-update-on-plugin-security/#a-technology-change
At the moment there is no DOM access in WASM, but there are proposals in progress to move towards support for that. Once that support is added, will WASM still be effectively isolated? Or is it only isolated because the attack vectors haven't been enabled yet?
Beta Was this translation helpful? Give feedback.
All reactions