- From: Prince via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Aug 2023 14:54:43 +0000
- To: public-css-archive@w3.org
I agree with you that it is illogical that the first value of the border-start-start-radius property is applied to the horizontal axis in both horizontal-tb and vertical-lr writing modes. The logical meaning of the property is to define the radius of the corner between the block-start and inline-start sides of the element, regardless of the writing mode. However, the physical meaning of the property is to define the radius of the corner between the top and left sides of the element, regardless of the writing mode. The reason for this behavior is that the border-start-start-radius property is a legacy property that was defined before the concept of writing modes was introduced to CSS. As a result, the property was not designed to take into account the different ways that text is laid out in different writing modes. There are a few solutions to this problem. One solution is to use the border-radius property instead of the border-start-start-radius property. The border-radius property takes four values, one for each corner of the element. This allows you to specify the radius of each corner independently of the writing mode. Another solution is to use the writing-mode property to switch to a writing mode where the logical and physical axes are the same. For example, **you could switch to the vertical-rl writing mode**, in which case the border-start-start-radius property would behave as expected. Finally, you could also write a custom CSS rule that maps the values of the border-start-start-radius property to the appropriate physical axes based on the writing mode. This would be the most complex solution, but it would give you the most control over the behavior of the property. I hope this helps! -- GitHub Notification of comment by ft-prince Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9217#issuecomment-1688350598 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 August 2023 14:54:46 UTC