[css-overflow] Questions regarding breaks in ellipsis strings
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
-
Regarding
block-ellipsis, the current spec says "The UA must treat the block overflow ellipsis as an unbreakable string" [1]. Is it referring to line breaking only, or also bidi re-ordering and fragmentation? I don't see anything wrong with allowing bidi reordering in the ellipsis string. -
Regarding
text-overflow, the current spec text doesn't mention anything about breaks. Should we add the same requirement asblock-ellipsis, namely, no linebreaking is allowed? Currently, only Firefox supports custom ellipsis strings, and FF ignores forced breaks there.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Overflow 4 block-overflow-ellipsis section linked in the issue, then compare its break-handling language with the text-overflow section. Determine whether the requirement covers line breaking, bidi reordering, and fragmentation, and whether text-overflow needs an equivalent rule; done means a resolved specification decision and corresponding wording.
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
- Mostly clear
- Newbie friendliness
- 35/100