Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Screenresolution vs. Browserresolution #312

Open
3 tasks
wurzelkuchen opened this issue Nov 19, 2024 · 0 comments
Open
3 tasks

Bug: Screenresolution vs. Browserresolution #312

wurzelkuchen opened this issue Nov 19, 2024 · 0 comments
Labels
bug docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made Low Priority

Comments

@wurzelkuchen
Copy link
Contributor

Quick Description

We had a request, about our browse config property screenresolution. In the example config we provide examples which use screenresolution instead of browserresolution. This leads to the confusing issue, that the browser starts in default size without any notification. Also our documentation on this property is not very herlpfull.

Actual Behaviour

If I use a browser config from the examples it should size the browser as configured.

Expected Behaviour

Some browser configs from our browser.properties are using default values instead of the expected values due to wrongfully used keywords.

Tasks

  • Clean up browser.proerties and use the correct browserresolution configs
  • Improve documentation (especially inside the browser.properties) and make clear, that screenresolution is only valid for emulation envorinments like browserstack
  • Check our example test suites, and fix/improve the browser.properties there as well if needed
@wurzelkuchen wurzelkuchen added bug Low Priority docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug docsNeeded The documenttion needs to be checked if there are changes needed and if so, adaptions should be made Low Priority
Projects
None yet
Development

No branches or pull requests

1 participant