Pure CSS dark-mode toggle:

https://www.draketo.de/software/css-dark-mode-toggle

The simplest pure #CSS toggle for dark mode without persistency. Commented example. Just read the code ☺.

#webdev #noJS

Pure CSS dark-mode toggle (no JS)

Verstreute Werke von ((λ()'Dr.ArneBab))

Wer so'n shice programmieren kann, kann auch gefälligst ne Seite baun die ohne #JavaScript auskommt!

#NoJS #Malware #NoJavascript #Accessibility #Privacy #ITsec #InfoSec #OpSec #ComSec #Webdesign #Enshittification

Just fucking use HTML

Stop reinventing the wheel. The web was doing just fine before your bloated frameworks crawled out of the sewer.

Just fucking use HTML

This is almost certainly not the right way to do this, but damn it is cool that you can.

https://dev.to/madsstoumann/guitar-chords-in-css-3hk8

#CSS #NoJS

Guitar Chords in CSS

In my previous article, I looked into the new, improved attr() method in CSS. I was over the moon...

DEV Community

📰 Ya puedes leer el post.

🧐 ¿Para qué usar 40kB de JavaScript cuando HTML ya lo resuelve con 4 líneas?

🪗 Si tu componente colapsa usando JS... tal vez nunca fue un buen componente.

👉 https://www.baumannzone.dev/blog/acordeones-nativos-en-html-sin-una-linea-de-javascript

#NoJs #HTML #a11y

Acordeones nativos en HTML sin una línea de JavaScript

Aprende a crear acordeones accesibles y funcionales utilizando solo HTML, sin necesidad de JavaScript

https://codepen.io/ItsDanQ/full/WbbymbB

This was fun but pointless: using #CSS :has(), :checked, and the subsequent sibling selector (~) to make a #noJS #HTML list filtering tool.

🔗 Blog post with more details: https://danq.me/dynamic-filters-in-pure-css

CSS List Filtering (no JS)

...

Minimal CSS-only blurry image placeholders

someone on here wished "there was an easy way to generate http errors" and now there is: https://http.xvrqt.com/

just go to /<status_code> to generate it (provided it's 200, or in the 4XX, 5XX range)

#html #css #nojs #http #codes #errors
HTTP Status Codes

A list of HTTP status codes. The error codes also provide the selfsame HTTP error code on their respective pages.

I think we may be passed the threshold where we can accept #NoJS anymore. What we do need is to actually look at #WebStandards and expand how containerized a website gets.

Like for instance, the app should not know the absolute value of your screen size, or to have so much control over #LocalStorage.

We're at a point where we should also ask ourselves if the #user shouldn't get to decide how they source their frameworks, be it from origin or from a #CDN.

@ngz0 @tbernard @niccolove

@janl #noJs is still a thing? haven't seen any real world requirement for that in maybe 10 years. tell me more!