Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-backgrounds-4] Define background-repeat|position longhands with a logical property group #11139

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

cdoublev
Copy link
Collaborator

@cdoublev cdoublev commented Nov 1, 2024

Follow-up on #116 (comment).

For example, flow-relative and physical background-position-* need to be in the same logical property group in order to maintain the appropriate order of declarations within a CSS declaration block, eg. with style.cssText = 'background-repeat: repeat; background-repeat-block: no-repeat; background-repeat-y: repeat'.

Cf. serialize a CSS declaration block and set a CSS declaration.

@fantasai fantasai merged commit e82ece6 into w3c:main Feb 27, 2025
1 check passed
@cdoublev cdoublev deleted the patch-5 branch February 27, 2025 05:08
tidoust added a commit to tidoust/csswg-drafts that referenced this pull request Mar 3, 2025
…erty group

The `background-position` longhands were already defined with
`background-position` as a logical property group. w3c#11139 duplicated the
"Logical property group" line in the property definition table, leading to
`background-position background-position` as logical property group in the
rendered spec.
tabatkins pushed a commit that referenced this pull request Mar 7, 2025
…erty group (#11810)

The `background-position` longhands were already defined with
`background-position` as a logical property group. #11139 duplicated the
"Logical property group" line in the property definition table, leading to
`background-position background-position` as logical property group in the
rendered spec.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants