[api-minor] Remove the separate enableScripting
option in BaseViewer
#13816
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.
Prior to PR #13042, when scripting wasn't really possible to use outside of the full viewer, the
enableScripting
option made sense.However, at this point in time having to both pass in a
PDFScriptingManager
-instance and set theenableScripting
-boolean when creating aBaseViewer
-instance feels redundant and (mostly) annoying. Hence this patch, which removes the separate boolean and always enables scripting whenscriptingManager
is provided.The relevant "viewer component" examples are also updated (with a comment), but in such a way that scripting support won't just break when used with the current PDF.js releases.