A syntax proposal for Cascade Layers #4470. This does not include full discussion of the Cascade Layer purpose and use-cases, which can be found in the various linked issues, but attempts to answer many of the outstanding questions about how we might implement a layering feature.
Collaborators:
| #!/usr/bin/env node | |
| const readline = require('readline'); | |
| const { execFileSync } = require('child_process'); | |
| const [minutes, yes] = process.argv.slice(2); | |
| const interval = 60 * 1000 * minutes; | |
| const cwd = process.cwd(); | |
| if (!minutes || parseInt(minutes) === NaN) { |
by Tatiana Mac
Last updated 14 April 2021
As speaking comes with immense privilege, I have crafted a speaker rider to set expectations and boundaries around my engagement. I am grateful to all the conference organisers who have brilliantly hosted me. I would love to continue to exercise this privilege to speak at conferences, and use this privilege to make the landscape more accessible and beneficial to tech's most historically excluded and marginalised communities.
😫 I provide a lot of explanations for those of you who never had to consider these things. Most thoughtful conferences I've attended check most of these boxes intrinsically, particularly when conference runners are experienced speakers. They get it.
| /* This special class is used to remove content visually, | |
| without removing it from screen reader output. Use it in | |
| place of `display: none` when you want screen readers to | |
| identify and announce the information the (visually) hidden | |
| element contains */ | |
| .vh { | |
| clip-path: inset(100%) !important; | |
| clip: rect(1px, 1px, 1px, 1px) !important; | |
| height: 1px !important; |
