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.

Sign up for GitHub

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

Jump to bottom

Use legacy name alias concept #121

Open
miketaylr opened this issue Mar 12, 2020 · 1 comment
Open

Use legacy name alias concept #121

miketaylr opened this issue Mar 12, 2020 · 1 comment
Assignees
@miketaylr

Comments

@miketaylr
Copy link
Member

https://drafts.csswg.org/css-cascade-4/#legacy-name-alias

When the old property’s syntax is identical to or a subset of the value space of the new property’s syntax, the two names are aliased with an operation on par with case-mapping: at parse time, the old property is converted into the new property. This conversion also applies in the CSSOM, both for string arguments and property accessors: requests for the old property name transparently transfer to the new property name instead.

Perhaps we can use this instead of the concept of simple property alias.

(cf @zcorpan's suggestion in w3c/csswg-drafts#4839)
This was referenced Aug 2, 2021
Closed
Closed
@miketaylr
Copy link
Member Author

Helpful pointer from @gsnedders, #154 (comment)
@miketaylr miketaylr self-assigned this Aug 6, 2021
miketaylr added a commit that referenced this issue Aug 6, 2021
@miketaylr
Issue #121 - Use legacy name alias concept as defined by CSS
dd9aa8a 
https://drafts.csswg.org/css-cascade-5/#aliasing
miketaylr added a commit that referenced this issue Aug 10, 2021
@miketaylr
Issue #121 - Use legacy name alias concept as defined by CSS (#155)
237bc41 
https://drafts.csswg.org/css-cascade-5/#aliasing
@karlcow karlcow mentioned this issue Jun 27, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@miketaylr and others