🐛 Fix enableJavaScript default for snapshot discovery #453
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.
What is this?
During the recent discovery/snapshot refactors, the
Page
class was updated to defaultenableJavaScript
totrue
for other packages to borrow a page without explicitly enabling it. However, sinceenableJavaScript
did not have a default configuration value for dom snapshots in thePercy
class, that resulted in all snapshots defaulting to have javascript enabled during asset discovery (this does not affect the API default).I also noticed that for snapshot captures, JavaScript is always enabled, even if the config option is
false
.I updated this line to always prefer the
enableJavaScript
option and default based on the presence ofdomSnapshot
. When there is no dom provided, the default should betrue
, otherwise it should befalse
. I also added a test so this can be caught in the future if it regresses again.