csstools / csstools/postcss-plugins
CSS Values lvl 5, standard if() syntax
- Lingua principale
- CSS
- Stelle
- 1.1k
- Fork
- 83
- Merge medio
- 10h 16m
- PR unite (30g)
- 16
Descrizione
### What would you want to propose?
Spec: https://drafts.csswg.org/css-values-5/#if-notation
This is the draft for a standard conditional selector.
There is a plugin that does similar thing called postcss-conditional-values, it could either be modified to support new experimental syntax, or a new plugin could be made partly based on it.
Would be nice to have a polyfill for this in the future with the standard syntax.
### Suggested solution
Spec allows media queries, and overall it is differs from postcss-conditional-values in a number of ways, so a new plugin is probably better.
Spec allows stuff like this:
```css
.valid-if {
--if-clause: media(width >= 600px): blue;
color: if(...var(--if-clause); else: green;);
}
```
I don't think is something that can be polyfilled
### Additional context
Overall this is more of a different syntax for queries, and doesn't replace postcss-conditional-values.
This request is related to https://github.com/csstools/postcss-plugins/issues/134 for some part.
### Validations
- [x] Follow our [Code of Conduct](https://github.com/csstools/postcss-plugins/blob/master/CODE_OF_CONDUCT.md)
- [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
### Would you like to open a PR for this feature?
- [ ] I'm willing to open a PR
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by reading the CSS Values Level 5 if() notation specification and comparing it with the existing postcss-conditional-values plugin. The issue does not name files, tests, or a defined implementation scope; done would require agreeing whether a new plugin can support a useful subset of the standard syntax and how that scope should be validated.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- css
- Ambito
- frontend, web-dev
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100