w3c / w3c/csswg-drafts

[css-ruby] How is additional leading calculated?

Open
#5,963 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

css-ruby-1
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

https://drafts.csswg.org/css-ruby/#line-height says:

However, if the line-height specified on the ruby container is less than the distance between the top of the top ruby annotation container and the bottom of the bottom ruby annotation container, then additional leading is added on the appropriate side(s) of the ruby base container such that if a block consisted of three lines each containing ruby identical to this, none of the ruby containers would overlap.

I think this is bit fuzzy in two ways:

  • "top of the top to bottom of the bottom", as well as line-height aren't just abstract distances, but positioned segments, so one can be smaller than the other and still stick out
  • I am not convinced that determining what side(s) is appropriate is self-evident

(@dbaron was also concerned about that text in https://lists.w3.org/Archives/Public/www-style/2014Dec/0366.html, though the specifics of his concerns are somewhat outdated due to more recent edits clarifying a few things)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the CSS Ruby line-height section linked in the issue, then review the cited 2014 www-style discussion and the issue's existing comments. Done means resolving how the distances and appropriate side(s) are determined, with the specification text made precise.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.