See links like https://openqa.opensuse.org/tests/1784596#step/logpackages/4 . When walking over screenshot thumbnails in the openQA test details page the preview appears with a nice arrow below the thumbnail. Selecting a text box looks quite different, with no arrow and the line breaking the list of steps displayed.
- AC1: Screenshot and text view behaviour is confirmed to be consistent by multiple power users
- Discuss with mkittler the options after mkittler did the new text preview implementation
- Ask multiple users if they like the behaviour, e.g. based on a video, a test instance or screenshots
- Don't add more AJAX but prefer a CSS-only solution
- Ensure the current flow of thumbnails and text boxes stays consistent
- Screenshot boxes currently hover on top, but text boxes don't. Both should behave the same. And both should have the little arrow to indicate which result is shown (maybe it would even look better with an additional dark effect like here.
Discuss with mkittler the options after mkittler did the new text preview implementation
I remember that last time I changed the behavior we didn't want to spend too much time on improving it further but of course that's still an option. When I remember correctly, I did the following improvements:
- The code for displaying finished results and the code for displaying results while the test is running should now be unified.
- There's no further AJAX request required when clicking on a text thumbnail.
- The expanded preview of a text thumbnail is more consistent with the way we display text results from external test suits.
I'd say that 1. and 2. should stay this way but of course 3. is something we might want to re-think. At least adding the arrow there as well would make sense.
Yes, the arrow should get added.
I would also like to see the rest of the current result row (which is currently only displayed below the currently selected result) as otherwise the next step is not directly visible for the reviewer.
They would be shown below, but depending on the size of the result box, this would require scrolling around and is also not consistent with the rest of the results, where the line is not broken.