atob function failing in IE11 and pre-Chromium Edge

[LordGalahad]

It seems that I cannot load custom fonts in IE11 or pre-Chromium Edge.

My Project selects a font file and then converts it into a Base64 string

I have no problems running this into Chrome or FireFox.

But when it came to IE11 or old Edge, I get that PubSub error with an invalid calling object details.

I tried to debug and and ended up here

atob was returning an invalid calling object error (does not happen in Chrome or Firefox)

A workaround I did was instead of fetching the font into a Blob and using a FileReader to get the Base64 string of the font. I used arrayBuffer and just use this:

let fontData = new Uint8Array(content).reduce((data,byte)=>(data.push(String.fromCharCode(byte)),data),[]).join('');

It worked, and then I remembered I also had a lot of images in Base64 string that resulted in Corrupted PNG.

[HackbrettXXX]

If I understand your description correctly, you are not reporting a bug in jsPDF but describing how you created a valid Base64 string from a blob? If you think this is a bug in jsPDF please share a complete repro.

FYI, instead of creating a Base64 string, you can also pass a binary string.

[LordGalahad]

Yeah my current workaround right now is passing a binary string instead. And yeah, it works this way. I guess we are too used to Base64 because we transport a lot of stuff to the server. But since everything is client side I think this is ok.

I may report this as an issue, but with IE11 being dropped next year and EDGE being placed by the Chromium Version, I will try to consult with my team about the priority of this one.

Weird though that when I called atob on my side I encounter no problems. But when I pass the Base64 string over to jspdf the problem occurs when the atob inside there is invoked.

[HackbrettXXX]

Ah I can imagine why it doesn't work in IE/Edge. We call atob without "this". The fix should be easy. I'm preparing a pull request.

[HackbrettXXX]

Could you check if the fix really resolves the issue (run npm run build first)?

[LordGalahad]

Could you check if the fix really resolves the issue (run npm run build first)?

Thanks. It is working now 👍

[HackbrettXXX]

Great!