- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Apr 2020 11:34:49 +0000
- To: public-css-archive@w3.org
I'd like to mention that this is not what Firefox currently does. Firefox's model is: when positioning ruby annotation containers of segment, it starts from the outside of all ruby annotation containers of inline ruby containers nested inside the ruby base container of that segment. Implementation-wise, it's done the way that after reflowing a ruby container, the total leadings created outside the ruby base container would be recorded and reported to the closest inline ruby base container ancestor, and when positioining ruby annotation containers, such leadings would be taken into account. Having written that, I think the implementation doesn't actually match the model I described above in the way that if the inner base has different font size than the outer base, it would be wrong... but playing with Firefox's implementation I don't see such bug... I'm now confused... -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4980#issuecomment-621777794 using your GitHub account
Received on Thursday, 30 April 2020 11:34:50 UTC