{"action":"created","issue":{"url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/81","labels_url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/81/labels{/name}","comments_url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/81/comments","events_url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/81/events","html_url":"https://github.com/jenkinsci/build-pipeline-plugin/pull/81","id":103940422,"number":81,"title":"[JENKINS-28180] The fluid layout has been improved to support long job names","user":{"login":"recena","id":1021745,"avatar_url":"https://avatars.githubusercontent.com/u/1021745?v=3","gravatar_id":"","url":"https://api.github.com/users/recena","html_url":"https://github.com/recena","followers_url":"https://api.github.com/users/recena/followers","following_url":"https://api.github.com/users/recena/following{/other_user}","gists_url":"https://api.github.com/users/recena/gists{/gist_id}","starred_url":"https://api.github.com/users/recena/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/recena/subscriptions","organizations_url":"https://api.github.com/users/recena/orgs","repos_url":"https://api.github.com/users/recena/repos","events_url":"https://api.github.com/users/recena/events{/privacy}","received_events_url":"https://api.github.com/users/recena/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-08-30T19:03:40Z","updated_at":"2015-08-31T11:43:35Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/pulls/81","html_url":"https://github.com/jenkinsci/build-pipeline-plugin/pull/81","diff_url":"https://github.com/jenkinsci/build-pipeline-plugin/pull/81.diff","patch_url":"https://github.com/jenkinsci/build-pipeline-plugin/pull/81.patch"},"body":"https://issues.jenkins-ci.org/browse/JENKINS-28180\r\n\r\n## Before\r\n![jenkins-28180_before](https://cloud.githubusercontent.com/assets/1021745/9568938/47839546-4f5a-11e5-9de9-fdee56ad1777.png)\r\n\r\n## After\r\n![jenkins-28180_before](https://cloud.githubusercontent.com/assets/1021745/9568950/80588b74-4f5a-11e5-8ce0-5ef43a2edcd1.png)\r\n\r\n@reviewbybees, specially @tfennelly "},"comment":{"url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/comments/136346667","html_url":"https://github.com/jenkinsci/build-pipeline-plugin/pull/81#issuecomment-136346667","issue_url":"https://api.github.com/repos/jenkinsci/build-pipeline-plugin/issues/81","id":136346667,"user":{"login":"tfennelly","id":429311,"avatar_url":"https://avatars.githubusercontent.com/u/429311?v=3","gravatar_id":"","url":"https://api.github.com/users/tfennelly","html_url":"https://github.com/tfennelly","followers_url":"https://api.github.com/users/tfennelly/followers","following_url":"https://api.github.com/users/tfennelly/following{/other_user}","gists_url":"https://api.github.com/users/tfennelly/gists{/gist_id}","starred_url":"https://api.github.com/users/tfennelly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tfennelly/subscriptions","organizations_url":"https://api.github.com/users/tfennelly/orgs","repos_url":"https://api.github.com/users/tfennelly/repos","events_url":"https://api.github.com/users/tfennelly/events{/privacy}","received_events_url":"https://api.github.com/users/tfennelly/received_events","type":"User","site_admin":false},"created_at":"2015-08-31T11:43:35Z","updated_at":"2015-08-31T11:43:35Z","body":"I agree with @recena wrt how the content is currently marked up using class names like `overflow-hidden` etc. That is bad practice. Also, how the CSS was applied globally to elements having that class name ... that's not ideal either.\r\n\r\nSo, I think the changes made by @recena probably do improve things, but I also hear what @oleg-nenashev is saying wrt custom CSS themes.\r\n\r\nOn the other hand, if we are saying that UI elements should never change for fear of breaking some custom theme, then I think we are effectively saying that we can never change UI, which would be crazy imo. In the case of this PR, it's not just the class name changes that could break a custom theme; the structural changes could too.\r\n\r\nSo:\r\n\r\n1. Is there a Jenkins policy around guaranteeing backward compatibility for custom themes? I'm not aware of one.\r\n1. In the case of this plugin, do we know of any custom themes that people might have that can't easily be \"fixed\" to work against the new layout."}}