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

In Chrome not able to click submit button which is not in view port. throws error "The element that matches the specified selector is not visible." #1353

Closed
gpsarkar opened this issue Mar 26, 2017 · 2 comments
Assignees
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@gpsarkar
Copy link

Are you requesting a feature or reporting a bug?

bug

What is the current behavior?

In Chrome browser, not able to click on submit button which is not in viewport.
Same test working on ie, firefox and edge.

What is the expected behavior?

Should be able to click submit button in Chrome browser

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

Run below test.

Provide the test code and the tested page URL (if applicable)

Tested page URL: http://testcafe.azurewebsites.net/Page2.htm

Test code

	await t
		.typeText(Selector('#ProposalName'), 'test 123')
		.typeText('#TitleInfo_Description', 'test')
		.wait(5000)
		.click('#startproposal');
    });

Specify your

  • operating system: Windows 10
  • testcafe version: 0.13.0
  • node.js version: v7.7.4
@AndreyBelym
Copy link
Contributor

AndreyBelym commented Mar 27, 2017

Hello @gpsarkar! I confirm the issue and I'm working on the fix now.

@AndreyBelym AndreyBelym added AREA: client SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug). labels Mar 27, 2017
@AndreyBelym AndreyBelym self-assigned this Mar 27, 2017
@AndreyBelym AndreyBelym added this to the Sprint #6 milestone Mar 27, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Mar 27, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Mar 27, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 10, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 12, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 14, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 14, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 14, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 17, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 18, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 19, 2017
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Apr 20, 2017
@lock
Copy link

lock bot commented Mar 29, 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 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: automations TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants