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

Resizing Chrome in emulation mode doesn't resize the whole window #2154

Closed
AndreyBelym opened this issue Feb 21, 2018 · 1 comment
Closed
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).

Comments

@AndreyBelym
Copy link
Contributor

Are you requesting a feature or reporting a bug?

Bug

What is the current behavior?

When starting e.g. chrome:emulation:device=iphone 6, and then calling resizeWindow in a test, the browser window is not resized, only emulated boundaries changed.

What is the expected behavior?

Window should be resized to match emulation boundaries.

How would you reproduce the current behavior (if this is a bug)?

Start testcafe "chrome:emulation:device=iphone 6". Call t.resizeWindow in a test.

Specify your

  • operating system: any
  • testcafe version: 0.19.0-alpha1
  • node.js version: 8.9.4
@AndreyBelym AndreyBelym added TYPE: bug The described behavior is considered as wrong (bug). SYSTEM: browser natives AREA: server labels Feb 21, 2018
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Feb 21, 2018
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 3, 2018
@AndreyBelym AndreyBelym reopened this Apr 16, 2018
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 18, 2018
AlexanderMoskovkin pushed a commit that referenced this issue Apr 19, 2018
* Cut screenshot mark from screenshots for elements (closes #2154)

* Fix warning message
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
…2154) (DevExpress#2327)

* Cut screenshot mark from screenshots for elements (closes DevExpress#2154)

* Fix warning message
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: browser natives TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

1 participant