[css-text-decor-3] Clarify expected computed value for `text-decoration` and similar shorthands (can we omit resolved `currentColor`?)
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
As of right now, text-decoration computed WPT expects text-decoration: none to be serialized to the resolved value of currentColor.
However, since currentColor is the default value of text-decoration-color, one might expect that we should omit it and the computed value should be none, following canonical order and short serialization rule, since none is the default value for text-decoration-line, which is the first longhand in canonical order.
For another similar shorthand property, text-emphasis that also has as a value of one of its longhands, It seems that for text-emphasis computed WPT, Safari, Chrome and Firefox agree that text-emphasis: none should be serialized to none <resolved-value-for-current-color>
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 by comparing the linked text-decoration and text-emphasis computed WPT results and the browser behavior described in the issue. Resolve whether resolved currentColor should be omitted, then update the relevant specification and WPT expectation once the CSSWG reaches a decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100