{"id":4650,"date":"2024-12-02T14:25:58","date_gmt":"2024-12-02T19:25:58","guid":{"rendered":"https:\/\/frontendmasters.com\/blog\/?p=4650"},"modified":"2024-12-04T16:21:03","modified_gmt":"2024-12-04T21:21:03","slug":"the-logical-border-radius-equivalents","status":"publish","type":"post","link":"https:\/\/frontendmasters.com\/blog\/the-logical-border-radius-equivalents\/","title":{"rendered":"The Logical Border Radius Equivalents"},"content":{"rendered":"\n

I find this hard to remember and it’s come up for me a few times lately so I’m writing it down gosh darn it!<\/p>\n\n\n\n

The individual corner border-radius<\/code> values, like border-top-right-radius<\/code> (which is hard enough to remember on its own) have logical property versions, meaning that should the flow of the document change, the border radius values should come along for the ride. <\/p>\n\n\n\n

border-top-right-radius<\/td>border-start-end-radius<\/td><\/tr>
border-top-left-radius<\/td>border-start-start-radius<\/td><\/tr>
border-bottom-right-radius<\/td>border-end-end-radius<\/td><\/tr>
border-bottom-left-radius<\/td>border-end-start-radius<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

(By “equivalent” I mean the these turn out the same in left-to-right, top-to-bottom languages like English, Spanish, French, etc. In other directional situations, these are not equivalent, which is kinda the point.)<\/p>\n\n\n\n

The syntax is:<\/p>\n\n\n\n

border-[block direction]-[inline direction]-radius<\/pre>\n\n\n\n
You’d choose the logical versions if you were using border-radius on elements where the flow was relevant. Here’s an example of a “tag” shape<\/a> on some inline text, and you’d potentially want<\/em> the direction to flip. <\/p>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
If border-radius is being applied entirely as an aesthetic thing and it makes more sense to apply physical directionality rather than text-flow directionality, which is entirely common, feel free to use the classic properties. <\/p>\n\n\n\n
I feel these newer logical properties for border-radius took an understandability hit, as while “border-top-right-radius” is hard to remember because of trying to remember the right order of the words, at least once you’ve got it, it’s clear where that radius is going to apply. Whereas with “border-start-end-radius” you just have to know (or guess and test) which direction “start” applies to and which direction “end” applies to.<\/p>\n\n\n\n
Something like border-inline-start-block-end-radius<\/code> would solve that, but I do understand that is an awfully long property name and might suffer from confusion. If someone accidentally mentally grouped it like “border-inline” “start-block” “end-radius”, that’s, uh, a meaningless jumble. <\/p>\n\n\n\n
There is an interesting gotcha Michelle Barker found in Logical Border Radius<\/a> with vertical writing modes, so if that comes up for you read what she’s got to say there. <\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
I find this hard to remember and it’s come up for me a few times lately so I’m writing it down gosh darn it! The individual corner border-radius values, like border-top-right-radius (which is hard enough to remember on its own) have logical property versions, meaning that should the flow of the document change, the border […]<\/p>\n","protected":false},"author":1,"featured_media":4657,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4650","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-post"],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/frontendmasters.com\/blog\/wp-content\/uploads\/2024\/12\/pexels-photo-22702715.jpeg?fit=1880%2C1253&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/4650","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/comments?post=4650"}],"version-history":[{"count":9,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/4650\/revisions"}],"predecessor-version":[{"id":4699,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/posts\/4650\/revisions\/4699"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media\/4657"}],"wp:attachment":[{"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/media?parent=4650"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/categories?post=4650"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/frontendmasters.com\/blog\/wp-json\/wp\/v2\/tags?post=4650"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}