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

[css-values] define parse-time value aliasing #6193

Closed
emilio opened this issue Apr 8, 2021 · 2 comments
Closed

[css-values] define parse-time value aliasing #6193

emilio opened this issue Apr 8, 2021 · 2 comments
Labels
Closed Accepted by CSSWG Resolution css-cascade-4 Current Work

Comments

@emilio
Copy link
Collaborator

emilio commented Apr 8, 2021

This is a thing which, just as property and selector aliases, exist. The later two are well defined, so we need to define this too.

Some examples in Firefox: https://searchfox.org/mozilla-central/search?q=parse%28alias&path=&case=false&regexp=false
@emilio emilio added the css-values-4 Current Work label Apr 8, 2021
@emilio emilio mentioned this issue Apr 8, 2021
Closed
@astearns astearns mentioned this issue Apr 8, 2021
Closed
@fantasai fantasai added css-cascade-4 Current Work and removed css-values-4 Current Work labels Oct 15, 2021
tabatkins added a commit that referenced this issue Oct 27, 2021
@tabatkins
[css-cascade-4][css-cascade-5] Add value-aliasing section. #6193
d29dc95
@fantasai
Copy link
Collaborator

Agenda+ to review the new section: https://drafts.csswg.org/css-cascade-4/#value-aliasing

@css-meeting-bot
Copy link
Member

The CSS Working Group just discussed [css-values] define parse-time value aliasing, and agreed to the following:

  • RESOLVED: Accept edits, expand to allow aliased functions
The full IRC log of that discussion <fantasai> Topic: [css-values] define parse-time value aliasing
<chris> miriam: is the changes section up to date?
<fantasai> github: https://github.com//issues/6193
<emilio> scribenick: emilio
<fantasai> fantasai: Added value aliasing section to cascade-4/5
<fantasai> emilio: Weird that it is scoped to keywords
<fantasai> fantasai: We didn't see any examples of not keywords, but could certainly reword to be more general
<emilio> emilio `-webkit-image-set()`-> `image-set()`
<emilio> Same with a bunch of gradient functions
<chris_> rrsagent, here
<RRSAgent> See https://www.w3.org/2021/11/17-css-irc#T17-27-14
<fantasai> fantasai: So functions and keywords, anything else?
<fantasai> s/scribenick: emilio//
<emilio> I don't _think_ so of the top of my head
<fantasai> astearns: So proposed to take edits, with additional change to add functions
<fantasai> fantasai: sgtm
<emilio> emilio: sgtm
<fantasai> RESOLVED: Accept edits, expand to allow aliased functions

@mozilla-apprentice mozilla-apprentice mentioned this issue Nov 17, 2021
Closed
fantasai added a commit that referenced this issue Dec 3, 2021
@fantasai
[css-cascade] Allow functional notation parse-time aliases as well. #…
b7345d7 
…6193
@fantasai fantasai closed this as completed Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Closed Accepted by CSSWG Resolution css-cascade-4 Current Work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fantasai @emilio @css-meeting-bot