w3c / w3c/csswg-drafts

[css-ruby] start/end-of-line white-space processing for annotations

Open
#6,002 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

For bases, how css-text start/end-of-line processing white-space applies is clear, since the base is in the main inline formatting context. However, for annotations, it is less clear.

Is css-text's start/end-of-line processing applied per segment/annotation container, or only to the start-most/end-most annotation containers in the ruby, or only to annotations at the start/end of the line, or not at all?

(For CJK, it would be fine to strip all spaces, but for Latin-based annotations, word separators are sometimes necessary, so this needs to be solved in consideration of that context.)

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 Text start/end-of-line processing rules and the CSS Ruby annotation/container definitions referenced in the issue. Compare whether processing should apply per annotation segment, at ruby edges, at line edges, or not at all, while accounting for CJK and Latin word separators; done means reaching a resolved specification behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Feature
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.