Scripted browser: Page load blocked due to webassembly


I attempted to write a simple scripted browser but during the validation I see it fails to load the our web application. I think the culprit is the fact that the page uses webassembly (we use it for text rendering) which is something that is blocked by the scripted browser by default. A similar page on this topic can be found here:

This is the code snippet I use:

var assert = require('assert');

    $browser.waitForAndFindElement($driver.By.className("scaling-dimensions"), 20000);

Can you enable webassembly for our account or suggest a workaround? This is a true showstopper for us, since it makes the synthetic monitoring functionality practically useless.

Thank you,

Hello @ukovac1.

Welcome to the community!

While it won’t be possible to enable this on your account, I am reaching out to our support engineers to see if there is a solution we can provide in your use case. We will reach back out here shortly and we appreciate your patience. Please reach out with any changes or questions you may have, we will be happy to help!

Hi @ukovac1

Unfortunately it’s true - the revelations in the post you found are still correct: New Relic doesn’t support WebAssembly.

I know it’s frustrating, but our engineers are aware and trying to find solutions. Currently, we do not have any work-arounds for pages using WebAssembly however.


1 Like