Accessible Inline Collapsible, by @erikKroes:
https://www.erikkroes.nl/blog/accessible-inline-collapsible/
Accessible Inline Collapsible, by @erikKroes:
https://www.erikkroes.nl/blog/accessible-inline-collapsible/
For the Love of “<details>”, by @developerjustin (@matuzo):
NoLoJS: Reducing the JS Workload With HTML and CSS, by @aarontgrogg (@perfplanet.bsky.social):
https://calendar.perfplanet.com/2025/nolojs-reducing-js-workload-html-css/
#html #disclosurewidgets #forms #modals #popovers #navigation #scrolling #positioning
NoLoJS: Reducing the JS Workload With HTML and CSS, by @aarontgrogg:
https://calendar.perfplanet.com/2025/nolojs-reducing-js-workload-html-css/
#html #disclosurewidgets #forms #modals #popovers #navigation #scrolling #positioning
Should We Even Have “:closed”?, by @sunkanmifafowora.bsky.social (@csstricks):
“::details-content”: Style Expandable Content Without Wrapper Divs, by @trevorlasn.bsky.social:
https://www.trevorlasn.com/blog/details-content-pseudo-element
Do you think, too, that disclosure widgets (`details` element) need stronger signaling they’re clickable?
Adding `summary { cursor: pointer; }` already makes for better affordance, but I wonder, would there be interest (and what’s the path) to include this in user agent styles?
Rethinking Cookie Dialogs, by @nattarnoff.bsky.social:
https://tarnoff.info/2025/10/06/rethinking-cookie-dialogs/
#accessibility #disclosurewidgets #html #cookies #consentmanagement
Let’s Play Accordion With the HTML “details” Element, by @alex86:
Can Native Web APIs Replace Custom Components in 2025?, by @dxnny.fun (@logrocket.bsky.social):
https://blog.logrocket.com/can-native-web-apis-replace-custom-components-2025/