Fix: custom fonts support on the Browser #2898
Open
+5
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, it's not possible to embed custom fonts when generating a docx from a Browser without polyfilling Buffer because the obfuscator uses native Node.js Buffers without checking for their availability.
This PR makes the obfuscator use Uint8Arrays instead of Buffers, so that it can also work in the Browser without polyfilling.
I also renamed the related tests file because there was a small typo.
Resolves: #2667