-
Notifications
You must be signed in to change notification settings - Fork 3
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
Uptime not handling different sized screenshots (mobile) particularly well #339
Comments
|
Should not have jumped in early without seeing the full screenshots. This is not related to synthetics agent, Probably a UI bug. I was referring to the black borders around the image which you wont see for any desktop screenshots. |
@andrewvc how does it look when you expand the row? IIRC the original complaint in this issue was that the image rendered way incorrectly for "portrait" aspect ratios (per the GIF in the issue description). While the image in the row does look somewhat goofy compared to desktop screenshots, we never changed that rendering as a part of this fix. I think if we did make it so the rows didn't grow at all for the thumbnail, it might be really tough to make out detail. |
We confirmed that the original issue (of not being able to see the full height of the image) is still working in 7.15. |
elastic/synthetics#371 raised to cover the separate issue of the border that is sometimes visible with some viewports. |
Kibana 7.14 (local, checked with build just now)
When using mobile device emulation in a Synthetics test, for example with:
Uptime has trouble showing the different sized image in some places.
Hovers and clicks to see the big (non thumbnail) image seems to be ok
Click to expand
Test result history seems ok:
Click to expand
Clicking through to a test result seems ok
Click to expand
However, expanding the step does not give enough space for the image:
(in this animation, I have scrolled all the way to the bottom of the screen, but the image is being chopped off.
The text was updated successfully, but these errors were encountered: