You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do a run of our test suite on small resolution, and in some cases we get the following issue:
We check an element which causes the screen to scroll. It scrolls just enough for another element to still be inside the viewport, but behind the fixed top navbar. When we then try to click this second element, canopy won't scroll up to reveal it, it just fails with "Timed out!" after a bit.
We have started scrolling to the top of the page in a few of our tests, but as this has been happening quite a few times on different device sizes for different tests, it's starting to feel like we are polluting our code a bit.
Is there an elegant way to solve this? Or maybe make a change in canopy where if an item is inside the viewport but behind another element, try to scroll it to the middle of the viewport before interacting with it?
The text was updated successfully, but these errors were encountered:
We do a run of our test suite on small resolution, and in some cases we get the following issue:
We check an element which causes the screen to scroll. It scrolls just enough for another element to still be inside the viewport, but behind the fixed top navbar. When we then try to click this second element, canopy won't scroll up to reveal it, it just fails with "Timed out!" after a bit.
We have started scrolling to the top of the page in a few of our tests, but as this has been happening quite a few times on different device sizes for different tests, it's starting to feel like we are polluting our code a bit.
Is there an elegant way to solve this? Or maybe make a change in canopy where if an item is inside the viewport but behind another element, try to scroll it to the middle of the viewport before interacting with it?
The text was updated successfully, but these errors were encountered: