Don't provide the enableXfa
parameter to the BaseViewer
constructor, and avoid the fallback bar with enableXfa = true
set (PR 13069 follow-up)
#13125
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.
Given that the
enableXfa
parameter must to be passed to the API/Worker, and thus included in thegetDocument
call, it's not necessary to include it when initializing thePDFViewer
-instance used in the default viewer. (Also, inAppOptions
, the parameter is clearly marked withOptionKind.API
.)Furthermore, we probably don't want to display the fallback bar (in Firefox) for XFA documents when
enableXfa = true
is set.