-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-ruby] Style of intra-annotation white spaces #5962
Comments
I think we could solve this in one of two ways:
The first of these two seems simpler. The second one would give more consistent spacing when some bases have a different size / font, which might be nice, but it's unclear how much that matters. Directly messing with their height contribution is probably not the answer here, as that wouldn't take care of how wide the space should be, which is also font / font-size dependent. |
(also, this was discussed in the 2015 Sydney F2F) |
@upsuper , I noticed such issue myself in your own test: http://wpt.live/css/css-ruby/ruby-intra-level-whitespace-001.html I created a more revealing test out of it: http://www.gtalbot.org/BrowserBugsSection/CSS3Ruby/ruby-intra-level-whitespace-001-GT.html
The default font size of rt element in the user agent style sheet is 50%. Anonymous rt elements will inherit their font size from the ruby container which uses a font size of 100%. So, there will be a height difference all the time. |
I forgot the whole context of that sentence when I sent it initially, but I'd like to note that it is possible for UA to style specific anonymous box they generate in a way which normal content is not able to access, i.e. if we want, I think it's possible to say that anonymous ruby annotation has 50% of the font size. But that has two problems:
I think in most common use cases, i.e. Japanese's kana annotation, it is not a problem, because there is generally no whitespace within the annotation between characters. |
(Initially reported by @upsuper in https://www.w3.org/Mail/flatten/index?subject=https%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fwww-style/2014Nov/0408.html )
The text was updated successfully, but these errors were encountered: