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 should be able to capture large views even if parts of it is outside bounds of the window. E.g. views inside ScrollView
Actual behaviour
Library captures only what is shown on the window and discards the rest of the view that is is outside the window
Steps to reproduce
Add multiple view(s) inside ScrollView until part of the ScrollVIew is placed outside the window then run the screenshot recorder task.
Version of the library
5.14.1
We can resolve the issue by providing viewHeight to compareScreenshot() method but that is not an actual solution. Problem is you will get this issue (#68) if provided dimension passes the limits set by library.
I can't really find any proper workaround for this problem, this is a major problem given you test your device in different resolutions and wonder why almost no care is given for such a big blocker.
The text was updated successfully, but these errors were encountered:
Expected behaviour
We should be able to capture large views even if parts of it is outside bounds of the window. E.g. views inside
ScrollView
Actual behaviour
Library captures only what is shown on the window and discards the rest of the view that is is outside the window
Steps to reproduce
Add multiple view(s) inside
ScrollView
until part of theScrollVIew
is placed outside the window then run the screenshot recorder task.Version of the library
5.14.1
We can resolve the issue by providing
viewHeight
tocompareScreenshot()
method but that is not an actual solution. Problem is you will get this issue (#68) if provided dimension passes the limits set by library.I can't really find any proper workaround for this problem, this is a major problem given you test your device in different resolutions and wonder why almost no care is given for such a big blocker.
The text was updated successfully, but these errors were encountered: