{"action":"created","issue":{"url":"https://api.github.com/repos/twbs/bootstrap/issues/19660","repository_url":"https://api.github.com/repos/twbs/bootstrap","labels_url":"https://api.github.com/repos/twbs/bootstrap/issues/19660/labels{/name}","comments_url":"https://api.github.com/repos/twbs/bootstrap/issues/19660/comments","events_url":"https://api.github.com/repos/twbs/bootstrap/issues/19660/events","html_url":"https://github.com/twbs/bootstrap/issues/19660","id":145277625,"number":19660,"title":"Padding & margins inconsistent between Bootstrap Elements","user":{"login":"timnicholson","id":96018,"avatar_url":"https://avatars.githubusercontent.com/u/96018?v=3","gravatar_id":"","url":"https://api.github.com/users/timnicholson","html_url":"https://github.com/timnicholson","followers_url":"https://api.github.com/users/timnicholson/followers","following_url":"https://api.github.com/users/timnicholson/following{/other_user}","gists_url":"https://api.github.com/users/timnicholson/gists{/gist_id}","starred_url":"https://api.github.com/users/timnicholson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timnicholson/subscriptions","organizations_url":"https://api.github.com/users/timnicholson/orgs","repos_url":"https://api.github.com/users/timnicholson/repos","events_url":"https://api.github.com/users/timnicholson/events{/privacy}","received_events_url":"https://api.github.com/users/timnicholson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/twbs/bootstrap/labels/css","name":"css","color":"563d7c"},{"url":"https://api.github.com/repos/twbs/bootstrap/labels/v4","name":"v4","color":"563d7c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-04-01T20:24:51Z","updated_at":"2016-09-30T19:22:49Z","closed_at":null,"body":"I'd like to better understand whether the existing v4 margin and padding classes as well as hx, p, etc. elements are going to remain the same or be adjusted at some point. The reason I ask is because it's practically impossible to get a content section with equal whitespace if a user is allowed to make any determination of which tags get used. This was the case with v3 as well. I'd love to see some consistency or at least better understand the reasoning behind these things.\r\n\r\nIn v4, it looks like the following is the case:\r\n- h1-h6 tags have their top-margin removed altogether. Is the assumption that each developer will set their own margins in their project? I can't imagine not wanting any top margin on hx tags, although I'd prefer they were consistent across all hx tags.\r\n- h1-h3? tags have 8px bottom margin while p tags have 16px bottom margin. What is the reasoning on this? Wouldn't it be better to have them the same? 8px is pretty short and 16px is pretty tall. \r\n- The new padding and margin classes end up being 16px, 32px, and 48px. Those don't align with the bottom margins above.\r\n\r\nSo there is no way to get a content area with equal whitespace on all sides without completely overriding everything.\r\n\r\nIn addition, containers and rows have 15px of whitespace, but gutter margins are 35px (although I get this probably has more to do with math than for the above items). Regardless, it really complicates things with trying to get consistent horizontal and vertical spacing.\r\n\r\nIn v3, things were/are still out of alignment:\r\n- h1-h3 tags have a top-margin of 22px and a bottom margin of 11px.\r\n- h4-h6 tags have a top-margin of 11px and a bottom margin of 11px.\r\n- p tags have a bottom margin of 11px.\r\n\r\nLet me provide an example. Let's say we just want equal top and bottom \"whitespace\". We'll forget about horizontal space for now. The new margin and padding classes don't allow us to deal with the 8px bottom margin of hx tags at all. \r\n\r\nI haven't completely thought through the perfect answer for this. Probably something like all hx tags having 16px top margin and 8px margin. Have all p and other tags have 8px bottom margin (or at least some consistent value). That way we could at least adjust the bottom whitespace of the div itself to get an even 16px on top and bottom. Of course we could then increase the whitespace on all sides of the div to get to other multiples, like 32px. \r\n\r\nAt any rate, I figured you guys were either still thinking this through and open to changes or had a really good explanation for why the values are set the way they are."},"comment":{"url":"https://api.github.com/repos/twbs/bootstrap/issues/comments/250830778","html_url":"https://github.com/twbs/bootstrap/issues/19660#issuecomment-250830778","issue_url":"https://api.github.com/repos/twbs/bootstrap/issues/19660","id":250830778,"user":{"login":"guylepage3","id":1711854,"avatar_url":"https://avatars.githubusercontent.com/u/1711854?v=3","gravatar_id":"","url":"https://api.github.com/users/guylepage3","html_url":"https://github.com/guylepage3","followers_url":"https://api.github.com/users/guylepage3/followers","following_url":"https://api.github.com/users/guylepage3/following{/other_user}","gists_url":"https://api.github.com/users/guylepage3/gists{/gist_id}","starred_url":"https://api.github.com/users/guylepage3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guylepage3/subscriptions","organizations_url":"https://api.github.com/users/guylepage3/orgs","repos_url":"https://api.github.com/users/guylepage3/repos","events_url":"https://api.github.com/users/guylepage3/events{/privacy}","received_events_url":"https://api.github.com/users/guylepage3/received_events","type":"User","site_admin":false},"created_at":"2016-09-30T19:22:49Z","updated_at":"2016-09-30T19:22:49Z","body":">So for example if they want 36px equal whitespace on all sides, they can use: p-x-3 p-t-3 p-b-2.\r\n\r\n@timnicholson I really like this idea."}}
{"actor":{"display_login":"guylepage3"}}