- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Mon, 23 Feb 2026 02:05:11 +0000
- To: public-css-archive@w3.org
> it only involves bopomofo and its tone marks (no latin or other text allowed) I completely agree that that's the intent, but here's the problem: HTML allows arbitrary content in the `<rt>` element. There is no way to force the markup to be limited to "up to 3 bopomofo charters and one tone mark". So even if it isn't meant to be used that way, we still must answer the question of what happens the markup contains other stuff, and css tries to apply that value. >> what if there's some non-bopommofo in there as well? > This is specifically for the bopoofo right-side rendering. So there won't be more than 3 character + 1 tone mark. Again, it *should not* be used with more than 3 characters+1 tone mark, but given how HTML works, it *can*. It's bad to use it this way, but we cannot prevent that, so we need to know what happens if someone does that. > Bottom line: this is not intended to be for positioning general content to the right of a character; it is expressly and specifically aimed at rendering standard bopomofo annotations in their normal right-of-base-character position. No disagreement as to the intent. Just saying: css applies to arbitrary HTML, so the behavior must be defined for arbitrary content. We do not have to go out of our way to make something "useful" outside of the recognized use-case, but the user agent will need to do something, and we should be clear on what that is. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13533#issuecomment-3942159297 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 February 2026 02:05:12 UTC