387 private links
In the meantime:
.visually-hidden:not(:focus):not(:active) {
border: 0;
clip: rect(0 0 0 0);
clip-path: inset(50%);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
white-space: nowrap;
width: 1px;
}
Using aliases are powerful to navigate in the terminal.
The author shares ad function to add... aliases on the fly
How to archive URLs and their content. It is a mine of tricks or information.
How to parse a programming language with typescript: here a small but working example
About 1.
- DOM refs created inside composables need to be explicitly destructured in setup() and returned. Otherwise, they won't be mapped to their DOM element.
Yes... but it is also the point that the template refs must be declared in the vue component. I find it more explicit IHMO. Imagine if multiple components were referencing multiple template refs.... It would add mental burden and forces the developer to know which composable use which refs.
About 2.
- Data inside refs isn't automatically usable by templates unless you wrap the composable invocation with reactive(), which conflicts with point 1 without even more destructuring.
Yes to get the value: const { myRef } = useComposable()
or
const r = reactive(useComposable())
I heard of it from the blog post: https://scottwillsey.com/astro-expressive-code/
It has an integration for Astro: https://github.com/expressive-code/expressive-code/blob/main/packages/astro-expressive-code/README.md
Basic validation can be done with HTML/CSS and the CSS selector :user-valid or :user-invalid pseudo-selectors
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /To favorise:
- checkbox
- file
- hidden
- radio
- password
- text
To avoid:
- button
- date
- datetime-local
- month
- number
- reset
- search
- submit
- time
- week
The rest is not sure or evident...
How do we actually encapsulate state, and actually regain compositional reasoning, fully? The technique that actually works is confining state locally. Confining state to within an object (“encapsulation” as it’s usually meant) doesn’t get us there because the state is owned by the object and thus escapes, but fully-local to a function does successfully isolate that state.
Resources to learn programming "in the large".
Resources to learn programming: in which order or why. Sources are different
On the part about algorithms:
We teach algorithms so that students learn to think about invariants and properties when writing code. Real-life code is usually simple enough that it mostly works if you just throw spaghetti onto the wall. But it doesn’t always work. To write correct, robust code at work, you need to think about invariants.
There is a list of algorithms too :)
And there is one site for every main programming topic: compilers, OS, ...
Update the styles of the web pages with custom ones :)
It contains all the gotcha we can find with the flow and cross axis, minimal width, align-content, margin auto, etc...
If a state is important enough to indicate visually, it's probably important enough to expose to assistive technologies.
With an example such as <a href="/about" aria-current="page" class="current-page">, we now have two meanings that convey the same information: the aria attribute and the class. This can leads to bugs while refactoring.
Another example is provided with dropdowns or toggle buttons, and sorted table columns.
Mentions to :disabled or aria-disabled, :invalid or aria-invalid, aria-selected, role="tab", and the list can go on!