[cssom] How to serialize 0% in translate property?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Gecko currently serializes 0% as specified in the translate property whereas Blink and WebKit omit it.
I think omitting it makes sense to follow the shortest form rule and to be consistent with how 0px is handled.
Though Gecko's motivation for the change was to be consistent with the translate() function for transform, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1566167#c7
This affects a few WPT:
- css/css-transforms/animation/translate-interpolation.html
- css/css-transforms/parsing/transform-valid.html
- css/css-transforms/parsing/translate-parsing-valid.html
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
Read the issue discussion and compare the affected WPT files: css/css-transforms/animation/translate-interpolation.html, css/css-transforms/parsing/transform-valid.html, and css/css-transforms/parsing/translate-parsing-valid.html. Check the linked Gecko context and current Blink/WebKit behavior before determining the serialization rule. Done means the specification decision is resolved and the relevant WPT expectations reflect it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100