A/B Test rasterizeHTML errors

Tim Rodham

Vote:

Seem to be getting a lot of 404 errors and "include.preload.js:344 Blocked script execution in 'about:blank' because the document's frame is sandboxed and the 'allow-scripts' permission is not set." from rasterizeHTML.js in the new A/B testing package.

Are these known bugs?

#171956

Nov 22, 2016 13:17

Magnus Eriksson

Vote:

Getting the same error. Any solution?

#172730

Dec 09, 2016 11:35

Drazen Stankovic

Vote:

Hi,

Have you managed to solve this problem?

Regards

#177137

Apr 04, 2017 12:50

mercedes

Vote:

Bumping this thread to see if anyone has managed to solve this issue.

#178347

May 09, 2017 17:59

Paul McGann

Vote:

We are having the same issue with an upgrade we have just done recently.

I tried this in a stand alone AlloyDemo with A/B Testing and the issue is here also.

I tried to allow-scripts in chrome to see if that would get around it but it didn't.

I then tried to unpackage the 'Episerver.Marting.Testing.zip' and updating the sandbox parameter to allow-scripts and this has now worked. Although I don't think this is a solution but it gets around the issue you can read more about the issues here https://github.com/cburgmer/rasterizeHTML.js/wiki/Limitations and there is an issue listed here https://github.com/cburgmer/rasterizeHTML.js/issues/117.

Thanks

#178501

Edited, May 11, 2017 22:56

Try our conversational search powered by Generative AI!

A/B Test rasterizeHTML errors