::selection ans ::backdrop does not inherit from root. So :root does not guarantee the CSS variable. The html selector does not solve this.

There is currently no global context in CSS, but root is the best workaround currently.

This is going to catch a lot of people off-guard because I, like many others, expect CSS Custom properties defined on :root to just be available everywhere.

The following discussion is there https://github.com/w3c/csswg-drafts/issues/6641

Here we go again with AI doing slop.

a pivot from “AI will find a cure for cancer” to “you can generate your own erotic nonsense video” be a perspective?

These four ways are footguns, but they can be easily spotted in the codebase.

Une certaine bonne nouvelle

Mostly financed by the GAFAM und tech industry. The same industry that harvest our personal data.

Vela dépend effectivement de la personne appelée. Je m'y retrouves https://blog.lyokolux.space/posts/21-09-01-chaque-generation-a-son-mode-de-communication-favori

Suite au vol des bijoux au musée du Louvre, la compagnie de l'élévateur lance une publicité pile au bon moment.

To enforce accessibility.

Also can poor performance be framed as inaccessible?

Le nom de code actuel est Bromo pour cette initiative

Plus de 70 Po (70 000 To) de données, 300 Po brutes

Les appareils Apple saturent le réseau pour la technologie AirDrop. Les appareils sautent de canaux toutes les deux secondes.

To prevent a custom behavior on Safari Mobile

A two day conference in Amsterdam

Another well written guide for Zod.

Cache-Control can set multiple directives:

• public and private
• max-age defines the amount of time until which the client can consider the response "fresh"
• must-revalidate indicates the HTTP cache should not reuse stale responses when they aer disconnected from the origin server
• no-store disable the cache for the request
• no-cache means ‘do not serve a copy from cache until you’ve revalidated it with the server and the server said you can use the cached copy’. no-cache will always hit the network as it has to revalidate with the server before it can release the browser’s cached copy. It will always hit at least an HTTP header response
• must-revalidate needs an associated max-age directive at which time the browser will revalidate.
• immutable avoid revalidation
• stale-while-revalidate provides is a grace period (defined by us in seconds) in which the browser is permitted to use an out of date (stale) asset while we’re checking for a newer version.
• stale-if-error provides a grace period if the server returns a 5xx error
• I overlooked s-maxage, proxy-revalidate, no-transform (useless for HTTPS) for proxies

Cache Busting strategies:

• no cache busting (dangerous) - style.css
• query string (does not work with proxies, i.e. Cloudflare) - style.css?v=1.2.14
• fingerprint - style.ae3f66.css

Fingerprinting is the best and allow the use of the immutable directive.
Not there is a new Clear-Site-Data: cache in case of need. Browser support is limited.

The post provide examples: Online Banking Page, Live Train Timetable Page, FAQs Page, Static JS (or CSS) App Bundle