Skip to content

Allow multiple position-area declarations for a single selector #302

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

Merged
merged 2 commits into from
Mar 28, 2025

Conversation

jgerigmeyer
Copy link
Member

Given:

.target {
  position-area: start;
}

.target {
  position-area: end;
}

Before, whichever one we parse last would be applied. Now this stores all of them, and allows the cascade to determine which one should be applied. (Or at least I think so -- some quick functional testing seemed to confirm that this works as expected.)

@jgerigmeyer jgerigmeyer requested a review from jamesnw March 28, 2025 20:45
Copy link

netlify bot commented Mar 28, 2025

Deploy Preview for anchor-position-wpt canceled.

Name Link
🔨 Latest commit d7fc4ba
🔍 Latest deploy log https://app.netlify.com/sites/anchor-position-wpt/deploys/67e70fb33ad50a0008727adb

Copy link
Contributor

@jamesnw jamesnw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent cleanup. Thanks!

@jamesnw jamesnw merged commit a6a107a into position-area Mar 28, 2025
8 checks passed
@jamesnw jamesnw deleted the pa-review branch March 28, 2025 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants