Description of problem: in some cases I cannot see statuses: in some I cannot: https://beaker.engineering.redhat.com/jobs/507893 in others I can: https://beaker.engineering.redhat.com/jobs/507595 Version-Release number of selected component (if applicable): 0.15 probably it's caused by those long names
As noted in bug 1014940, this results from the combination of a flexible width table but a fixed width overall viewport.
*** Bug 1014940 has been marked as a duplicate of this bug. ***
*** Bug 1014995 has been marked as a duplicate of this bug. ***
As noted in bug 1014995, this problem also used to occur with the previous UI, but caused the entire page to expand beyond the width of the browser window. That meant the *browser* scrollbar was triggered (and always visible), whereas the viewport scrollbar currently being triggered instead may be off the bottom of the screen for larger jobs.
The narrow viewport is also a problem for display of the job matrix and the system table with many columns selected. Given the historical behaviour and the fact this affects more screens than just the job results, simply letting the new UI expand to fill the browser window like the old one may be the best near term option.
Increasing the container to 100% is easy enough. http://gerrit.beaker-project.org/2350 I don't think it's a good permanent solution because it encourages building UIs which assume a really wide viewport (most of Beaker has this problem now, as we have seen) and conversely, if the UI *is* designed to behave reasonably in narrow viewports, it will typically be stretched out and/or too sparse and/or require too much horizontal eye scanning when it's displayed at 100% width in a wide viewport. But this might be a good near-term solution until we can improve the layout of some of the more problematic pages. As for the original problem in this bug report (very long result names which do not wrap) we could work around that by (ab)using the word-break CSS property to allow the browser to wrap the result name at any point. The overflow-wrap CSS property is actually the proper answer but that requires forcing a max-width on the table cells and there is no single width which will work well in all cases. http://gerrit.beaker-project.org/2352 Down the track I would still like to give the recipe results a broader overhaul to see if we can display results more efficiently than the current tabular layout.
Created attachment 811537 [details] screenshot for comment11
(In reply to Dan Callaghan from comment #9) > As for the original problem in this bug report (very long result names which > do not wrap) we could work around that by (ab)using the word-break CSS > property to allow the browser to wrap the result name at any point. This is not a suitable workaround because it ruins the word wrapping for result names which use hyphens instead of underscores. Currently those wrap correctly, with word-break: break-all; they will instead be wrapped in the middle of words which is not desirable.
I think the best we can do in the short term is override the overflow: auto; rule on the results tab content div. That way if the results table does overflow because of long result names using underscores, the viewport will be scrolled instead of the results tab (meaning the scrollbar will appear at the bottom of the window as before). http://gerrit.beaker-project.org/2361 By the way, I would strongly recommend you switch your result names to use hyphens instead of underscores to separate words, since they will be easier to read and the browser can wrap them properly if needed.
beaker 0.15.1 has been released.