Re-factor how the GenericL10n
class fetches localization-data
#17277
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.
Re-factor the existing
fetchData
helper function such that it can fetch more types of data, and it now supports "arraybuffer", "json", and "text". This only needed minor adjustments in theDOMCMapReaderFactory
andDOMStandardFontDataFactory
classes.[1]Expose the
fetchData
helper function in the API, such that the viewer is able to access it.Use the
fetchData
helper function in theGenericL10n
class, since this should allow fetching of localization-data even if the default viewer is run in an environment without support for the Fetch API.[1] While testing this I also noticed a minor inconsistency when handling standard font-data on the worker-thread.