Re: [csswg-drafts] [css-ruby] alternating sides for ruby-position (#5971)

Here's an example. It's a little contrived in order to keep it in English for readability's sake, but the same idea would apply, and be more common, in Japanese or Chinese.

```html
<ruby>
  <rb>S<rb>Q<rb>L</rb>
  <rtc><rt>Structured <rt>Querry <rt>Language</rtc>
  <rtc>Sequel</rtc>
</ruby>
```

This would look like this:

> <img width="214" alt="Screen Shot 2021-02-19 at 9 07 50" src="https://user-images.githubusercontent.com/113268/108438143-fb7c8c00-7291-11eb-92ea-37ee2a8c7c33.png">


However, when you have two levels of ruby, the typical expectation is that instead of stacking up, they go on alternate sides, like this:

> <img width="203" alt="Screen Shot 2021-02-19 at 9 07 41" src="https://user-images.githubusercontent.com/113268/108438163-046d5d80-7292-11eb-83b1-836d7b495ca1.png">


As the spec stands today, you can achieve it using `ruby-position`. For instance:
```css
rtc:last-of-type {
   ruby-position: under;
}
```

That's cool, but:
1. You have to ask for it explicitly, even though it's the most commonly desired outcome
2. The selector in the example above is specific to the markup pattern used in that example, and no generic selector that would work across all pages can be written (rtc and rt elements can, and typically are, omitted in most situations)

However, if instead of `over`, the initial value of `ruby-position` was `alternate` (a keyword we'd need to introduce), it would work outside of the box, without a need for manually opting into it.

The other variant being proposed is instead of `over | under | alternate`, we could have `[over | under ] || alternate`. `alternate` or `over alternate` would do the same as the above example (first annotation over, then alternate), while `under alternate` would put the first annotation under, and then alternate.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5971#issuecomment-781718791 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 19 February 2021 00:10:23 UTC