fixes #4173
Thanks in advance for your contribution. Please follow the below steps in submitting a pull request, as it will help us with reviewing it quicker.
[ . ] Before marking your PR for review, please test and verify your changes by making appropriate modifications to any of the Nightwatch example tests (present in examples/tests directory of the project) and running them. ecosia.js and duckDuckGo.js are good examples to work with.
[ . ] Create a new branch from master (e.g. features/my-new-feature or issue/123-my-bugfix);
[ . ] If you're fixing a bug also create an issue if one doesn't exist yet;
[ ] If it's a new feature explain why do you think it's necessary. Please check with the maintainers beforehand to make sure it is something that we will accept. Usually we only accept new features if we feel that they will benefit the entire community;
[ ] Please avoid sending PRs which contain drastic or low level changes. If you are certain that the changes are needed, please discuss them beforehand and indicate what the impact will be;
[ ] If your change is based on existing functionality please consider refactoring first. Pull requests that duplicate code will most likely be ignored;
[ ] Do not include changes that are not related to the issue at hand;
[ ] Follow the same coding style with regards to spaces, semicolons, variable naming etc.;
[ ] Always add unit tests - PRs without tests are most of the times ignored.
fixes #4173
Thanks in advance for your contribution. Please follow the below steps in submitting a pull request, as it will help us with reviewing it quicker.
examples/testsdirectory of the project) and running them.ecosia.jsandduckDuckGo.jsare good examples to work with.features/my-new-featureorissue/123-my-bugfix);