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.

Sign up for GitHub

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

Jump to bottom

TestCafe doesn't check visibility with timeout when target element style.top is negative #1185

Closed
georgiy-abbasov opened this issue Jan 27, 2017 · 1 comment
Closed

TestCafe doesn't check visibility with timeout when target element style.top is negative #1185

georgiy-abbasov opened this issue Jan 27, 2017 · 1 comment
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
Sprint #8

Comments

@georgiy-abbasov
Copy link
Contributor

georgiy-abbasov commented Jan 27, 2017 •
edited
Loading

Are you requesting a feature or reporting a bug?

bug

What is the current behavior?

TestCafe immediately fails, when tries to click on element which has next style:

#target {
    position: absolute;
    width:300px;
    height:300px;
    background:red;
    top: -9999px;
}

What is the expected behavior?

TestCafe should wait time, which specified in (options.timeout)[https://devexpress.github.io/testcafe/documentation/test-api/selecting-page-elements/selector-options.html#optionstimeout], till target element becomes visible

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

run test

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

Tested page URL:
page markup:

<!DOCTYPE html>
<html>
<head>
    <title>Title</title>
    <style>
        #target {
            position: absolute;
            width:300px;
            height:300px;
            background:red;
            top: -9999px;
        }
    </style>
</head>
<body>
<div id="target">
</div>
<script>
    window.setTimeout(function () {
        document.getElementById('target').style.top = '0px';
    }, 5000);
</script>
</body>
</html>

Test code

await t.click(Selector('#target').with({selectorTimeout: 10000}));

Specify your

  • operating system: WIN10 x64
  • testcafe version: 0.12.1
  • node.js version: 6.9.1
@georgiy-abbasov georgiy-abbasov added AREA: client SYSTEM: API TYPE: bug The described behavior is considered as wrong (bug). labels Jan 27, 2017
@georgiy-abbasov georgiy-abbasov added this to the Sprint #4 milestone Jan 27, 2017
@georgiy-abbasov georgiy-abbasov self-assigned this Jan 27, 2017
@georgiy-abbasov georgiy-abbasov changed the title Selector's options.visibilityCheck isn't working TestCafe doesn't check visibility with timeout when target element style.top is negative Jan 27, 2017
@georgiy-abbasov georgiy-abbasov removed this from the Sprint #4 milestone Feb 7, 2017
@inikulin inikulin added this to the Planned milestone Mar 21, 2017
@AlexanderMoskovkin AlexanderMoskovkin modified the milestones: Sprint #8, Planned Jun 9, 2017
AlexanderMoskovkin added a commit to AlexanderMoskovkin/testcafe that referenced this issue Jun 29, 2017
@AlexanderMoskovkin
Implement waiting element login inside automations (closes DevExpress…
0f88219 
…#1185)
AlexanderMoskovkin added a commit to AlexanderMoskovkin/testcafe that referenced this issue Jul 12, 2017
@AlexanderMoskovkin
Implement waiting element login inside automations (closes DevExpress…
a943c1c 
…#1185)
@AlexanderMoskovkin AlexanderMoskovkin mentioned this issue Jul 17, 2017
Merged
@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
@AlexanderMoskovkin @kirovboris
Improve waiting for element logic (closes DevExpress#1521) (DevExpres…
9370909 
…s#1582)

* Implement waiting element login inside automations (closes DevExpress#1185)

* add tests and spike implementation

* SelectChildAutomation small refactoring

* Click automation refactoring

* DblClick, Hover, RClick refactored

* Drag refactored

* Select action refactoring. Fix tests

* Remove redundant files

* Fix bootstrap case. Fix "pointer-events: none" case.

* Roll back "pointer-events: none" case. Fix svg case in IE

* Show status bar

* Minor refactoring

* Fix test

* Fix test

* Add tests for all automations

* Fix remarks

* Fix remarks

* Fix tests
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
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
Milestone
Sprint #8
Development

No branches or pull requests
3 participants
@inikulin @AlexanderMoskovkin @georgiy-abbasov