Add scripting and user preferences as Device
parameters
#259
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.
In working on #251, I realised that we're currently lacking scripting as a device parameter. This is needed to correctly handle rendering hints for the
<noscript>
element as they depend on whether scripting is enabled or not. This pull request therefore adds scripting as a device parameter and also adds user preferences as these are something we'll be needing.The changes introduced are breaking as they add two additional required properties to the
Device.JSON
type. Thejavascript
option for theScraper#scrape()
method has also been removed as theDevice#scripting
property now fulfils this need, and likewise has the--[no-]javascript
flag in the CLI been renamed--[no-]scripting
to align things.