w3c / w3c/csswg-drafts

[css-transforms-2] Syntax of individual transforms should reflect general CSS syntax

Open
#7,646 22 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-transforms-2
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

For example: Individual translate is only usable like so: translate: 0 0 10px
But translate as an individual property should be a shorthand for
translate-x, translate-y, and translate-z
In my opinion, this would reflect the current CSS syntax with other properties, like overflow, background-position, scroll-snap-type, and so on. Otherwise, it feels kind of inconsistent to me.

Or is there any technical reason that we cannot provide that syntax for individual transforms?

Spec: https://www.w3.org/TR/css-transforms-2/#individual-transforms

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 with the linked CSS Transforms Level 2 specification, especially the individual-transforms section, and review the issue discussion for the syntax proposal and technical constraints. Done means the CSS Working Group has resolved whether individual translate should follow the proposed shorthand syntax and the specification reflects the agreed decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.