alcinnz
/
PostJS
1
2
Fork 1
Code Issues Pull Requests Releases Wiki Activity

Update 'proposals/conditional-css.md'

This commit is contained in:
alcinnz 2018-11-29 16:46:13 -05:00
parent 60ab32b1e0
commit 8429fc9de6
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
proposals/conditional-css.md
View File

@ -19,12 +19,11 @@ So I propose that CSS should be extended such that style rules can be made condi
* Browsers should be free to choose not to implement this, if it doesn't work well with their UI devices.
### Required clarifications
* Need case studies links to clarify the needs for this.
* When should selector variables (as defined by Ankarstrom) be captured?
* They should be captured exclusively via attribute selectors of the parent in order to minimize complexity.
* How should layout conditions work?
* Conditions on numbers from the box-model would be intuitive.
* Conditions on ranges would be convenient without introducing additional complexity.
* Conditions on ranges would be convenient without introducing much additional complexity.
* Should be safe to test relative positions between elements, the viewport, and/or the cursor.
* Need to be cautious if these conditons can be used to impact where things are positioned AND these new positions can be tested against in another styling pass. That starts to at least resemble Turing Completeness.
* Ankarstrom suggested that having three variants (`while` which would be deactivated when the condition selector no longer matches, `on` which would not deactivate, and `toggled-by` which would deactivate when the selector next matches). Can we establish what these needs are?