Created attachment 519043 [details] patch Wide rows in jobs list don't make orientation easy. Thin are much better (and nicer) in my opinion. It is very good idea to apply patch from Bug 732024 before (or together with) this one. That patch provides coloring which is very helpful for orientation and will be important in case of thin rows. Attached patch wasn't tested, I haven't beaker instance for testing. I didn't even study beaker internals carefully. Please review it with care, avoid possible issues introduced be me. ;)
Apologies, these are being bumped to next maint release.
http://gerrit.beaker-project.org/#/c/1137/1
Created attachment 598548 [details] screenshot of padding on job page Export link on job page has weird left padding (see attached screenshot). Probably just needs class="job-action" removed from it on this page, or the CSS rule for job-action updated to be specific to the grid.
What's even worse, is that the only thing keeping the 'Clone Delete Export' on seperate lines is that the 'Delete' is now a block level element and clears both left and right. When we don't have 'Cancel' instead of 'Delete', they are all shown on the same line (ala the jobs page), which just looks wrong.
When we *do* have Cancel rather...
http://gerrit.beaker-project.org/#/c/1220/
(In reply to comment #6) > What's even worse, is that the only thing keeping the 'Clone Delete Export' > on seperate lines is that the 'Delete' is now a block level element and > clears both left and right. When we don't have 'Cancel' instead of 'Delete', > they are all shown on the same line (ala the jobs page), which just looks > wrong. Why do same elements have different rendering options? Patch in this bug just removed br tags and added brackets for better separation of links, neither padding nor any other formatting. Elements were all inline (despite to different classes assigned what is still little bit weird for unfamiliar person) and as far as I can say it is working quite fine. Why to not implement it that way?
(In reply to comment #9) > (In reply to comment #6) > > What's even worse, is that the only thing keeping the 'Clone Delete Export' > > on seperate lines is that the 'Delete' is now a block level element and > > clears both left and right. When we don't have 'Cancel' instead of 'Delete', > > they are all shown on the same line (ala the jobs page), which just looks > > wrong. > > Why do same elements have different rendering options? Patch in this bug > just removed br tags and added brackets for better separation of links, > neither padding nor any other formatting. Elements were all inline (despite > to different classes assigned what is still little bit weird for unfamiliar > person) and as far as I can say it is working quite fine. Why to not > implement it that way? The main reason why we got rid of the brackets is that similar actions on other pages use them, so we just thought we would try and keep it consistent. The only issue was that there was another change which changed 'Delete' to be a block level element, and so items would display differently depending on whether 'Delete' was shown or not.
Created attachment 599027 [details] This is with a narrow screen
Because of 822492, a whiteboard entry of sufficient size (or a narrow screen) can cause the action items to wrap. http://gerrit.beaker-project.org/#/c/1226/
Oops, I missed closing this bug. Beaker 0.9.1 was released last week.