See screenshot:
      The table for the build results may overlap the status output

          [JENKINS-23829] Layout: Job history may overlap main job status

          Update to Jenkins ver. 1.575 not fix the problem.

          In 575 still see:
          http://img-fotki.yandex.ru/get/6834/27441075.0/0_10ceca_252fc694_XXXL

          Kirill Merkushev added a comment - Update to Jenkins ver. 1.575 not fix the problem. In 575 still see: http://img-fotki.yandex.ru/get/6834/27441075.0/0_10ceca_252fc694_XXXL

          Daniel Beck added a comment -

          It'll be in 1.576.

          Daniel Beck added a comment - It'll be in 1.576.

          Wow - the new version (1.576) looks... lets say - awful. Sorry. I don't reopen the bug because maybe it's only me who want's the no-wrap back

          Suggest to use no-wrap in combination with overflow styles.
          When i edit the
          <div class="container-fluid pane-frame" id="buildHistory">
          with firebug to
          <div class="container-fluid pane-frame no-wrap" id="buildHistory" style="overflow-x:scroll">
          it looks better in my eyes.
          (see screenshot).

          Maybe you can think about this solution??

          Sven Appenrodt added a comment - Wow - the new version (1.576) looks... lets say - awful. Sorry. I don't reopen the bug because maybe it's only me who want's the no-wrap back Suggest to use no-wrap in combination with overflow styles. When i edit the <div class="container-fluid pane-frame" id="buildHistory"> with firebug to <div class="container-fluid pane-frame no-wrap " id="buildHistory" style="overflow-x:scroll" > it looks better in my eyes. (see screenshot). Maybe you can think about this solution??

          Daniel Beck added a comment -

          How did it look before the UI changes?

          Daniel Beck added a comment - How did it look before the UI changes?

          Tom FENNELLY added a comment -

          @Sven Appenrodt ... Your point/complaint seems to be different from what this JIRA is actually about. Anyway... the original version of the changes you are talking about hid the overflow (elipsis - revealing the full text as a hover tip). The reaction to that from others was along the lines of your reaction i.e. they didn't like it... they wanted to be able to see all the text without needing to hover or scroll etc etc. As the saying goes... "you can please some of the people some of the time...."

          By the way... I agree with your general comment... I too think it "looks" better without the overflow. However... I think saying it looks "awful" is OTT. Just say'n It's not that bad and, from a functional perspective, I get the objections that others have to hiding the overflow. I guess "looks" sometimes get trumped by other concerns.

          Since all these things are now in CSS, you can probably override using one of the skins plugins. Longer-term, I think it would be nice to have all these things in a global "Themes" config section, where you could specify your preferred behaviour.

          Tom FENNELLY added a comment - @Sven Appenrodt ... Your point/complaint seems to be different from what this JIRA is actually about. Anyway... the original version of the changes you are talking about hid the overflow (elipsis - revealing the full text as a hover tip). The reaction to that from others was along the lines of your reaction i.e. they didn't like it... they wanted to be able to see all the text without needing to hover or scroll etc etc. As the saying goes... "you can please some of the people some of the time...." By the way... I agree with your general comment... I too think it "looks" better without the overflow. However... I think saying it looks "awful" is OTT. Just say'n It's not that bad and, from a functional perspective, I get the objections that others have to hiding the overflow. I guess "looks" sometimes get trumped by other concerns. Since all these things are now in CSS, you can probably override using one of the skins plugins. Longer-term, I think it would be nice to have all these things in a global "Themes" config section, where you could specify your preferred behaviour.

          Sven Appenrodt added a comment - - edited

          @Daniel - Downloaded version 1.568 and i can see the side-panel was enlarged. (see screenshot)
          I think it depends on the former definition:

          <td width="10%" id="side-panel">
          and css:
          #side-panel {
          padding: 4px;
          width: 220px;
          }

          but i'm not an expert in html/css. I already made some experiments with the current jenkins-version like: change class col-lg-6 from width to min-width and col-lg-18 to max-width - and it worked - but i assume this has too much influence to the other pages (which i didn't tests because of the hard configuration with 'firebug').

          @Tom
          Sorry - maybe "awful" was a to hard word. The was supposed to tame it... I didn't reopen the ticket because it is closed correctly - so normally i should open a new task with a new description, linking this one. And i assume this will happen (and not by me). If you like we can discuss this via mail - i'm open to everything

          Sven Appenrodt added a comment - - edited @Daniel - Downloaded version 1.568 and i can see the side-panel was enlarged. (see screenshot) I think it depends on the former definition: <td width="10%" id="side-panel"> and css: #side-panel { padding: 4px; width: 220px; } but i'm not an expert in html/css. I already made some experiments with the current jenkins-version like: change class col-lg-6 from width to min-width and col-lg-18 to max-width - and it worked - but i assume this has too much influence to the other pages (which i didn't tests because of the hard configuration with 'firebug'). @Tom Sorry - maybe "awful" was a to hard word. The was supposed to tame it... I didn't reopen the ticket because it is closed correctly - so normally i should open a new task with a new description, linking this one. And i assume this will happen (and not by me). If you like we can discuss this via mail - i'm open to everything

          Daniel Beck added a comment -

          Sven: So the actual page content had less horizontal space when that happened, right. Wasn't that great of a solution either.

          Daniel Beck added a comment - Sven: So the actual page content had less horizontal space when that happened, right. Wasn't that great of a solution either.

          Tom FENNELLY added a comment - - edited

          @Sven hehehe no hard feelings at all... that was why I softened my comment with I'm glad you went to the bother of sending us your feedback because it does mater... we do take things like this into account. I think your comment reinforces (in me anyway) the idea that we need a "Themes" type global config where people can select their preferred behaviour in given situations e.g. select how you want overflow to be handled in sidepanels etc.

          In the end of the day... I know I use Jenkins less than a lot of people here, so I tend go with whatever feedback I get on things like this and that may result in "the squeaky wheel gets the oil" type of scenario.

          Tom FENNELLY added a comment - - edited @Sven hehehe no hard feelings at all... that was why I softened my comment with I'm glad you went to the bother of sending us your feedback because it does mater... we do take things like this into account. I think your comment reinforces (in me anyway) the idea that we need a "Themes" type global config where people can select their preferred behaviour in given situations e.g. select how you want overflow to be handled in sidepanels etc. In the end of the day... I know I use Jenkins less than a lot of people here, so I tend go with whatever feedback I get on things like this and that may result in "the squeaky wheel gets the oil" type of scenario.

          Tom FENNELLY added a comment -

          Btw.. I just created a JIRA for a "UI Themes" plugin: JENKINS-24353

          Tom FENNELLY added a comment - Btw.. I just created a JIRA for a "UI Themes" plugin: JENKINS-24353

          Daniel Beck added a comment -

          JENKINS-24589 is about the usability of forced narrow sidepanels and long entries. Maybe a better solution can be found. Further discussion there.

          Daniel Beck added a comment - JENKINS-24589 is about the usability of forced narrow sidepanels and long entries. Maybe a better solution can be found. Further discussion there.

            tfennelly Tom FENNELLY
            pedersen Björn Pedersen
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: