Adding WebViewer option xdomainProxyUrl causes Uncaught TypeError: Cannot read property 'statusText'

[Benjamin Roedell]

Adding WebViewer option xdomainProxyUrl causes Uncaught TypeError: Cannot read property 'statusText'

I've put my code here https://github.com/benrobot/benrobot.github.io

This link works OK without xdomainProxyUrl option passed to the WebViewer initializer: https://benrobot.github.io/?pdfToManipulate=resources%2FThis_pdf_file_needs_a_coverpage_and_watermarks.pdf&pdfCoverPage=%2Fresources%2FThis_is_a_cover_page.pdf

This link shows that stuff breaks when xdomainProxyUrl option is passed to the WebViewer initializer: https://benrobot.github.io/?pdfToManipulate=resources%2FThis_pdf_file_needs_a_coverpage_and_watermarks.pdf&pdfCoverPage=%2Fresources%2FThis_is_a_cover_page.pdf&includeXDomainJsOption=true

Here's what I think I know so far:

I think that xdomain.js is failing to modify the global object XMLHttpRequest and it leaves it as a useless object.  

The XMLHttpRequest seems to work fine before

<script src="external/xdomain.js" slave="https://c.na34.visual.force.com/apex/proxy"></script>

and after it is appended by the function exports.ControlUtils.initXdomain the XMLHttpRequest object doesn't look right (to me).

Many thanks for your help,

Ben

[Matt Parizeau]

Hi Ben,

Thanks for the example! Can you try modifying xdomain.js line 136 that has listener.apply(undefined, args); and change it to listener.apply(this, args);

I think "this" isn't being set correctly so it isn't the XMLHttpRequest object in a function that we expect it to be.

Matt Parizeau

Software Developer

PDFTron Systems Inc.

[Benjamin Roedell]

That solved it.  Thank you very much.