Just published: “Designing with Abstractions: CSS and the Case of Masonry Layouts”
This (academic) article explores CSS as both a technical system and a design object. It examines how this is shaped through negotiation between conceptual models, implementation constraints, and interface considerations, focusing on the Masonry layout debates.
Appreciation to those participating in CSS WG debates and making this work visible.
When applying a thick border around an element in multiple colors, the corners meet at a 45-degree angle forming a diamond. That is established and seems reasonable.
But, when you set a thick edge on one side, the thin 1px border gets squeezed into a slope, and won't reach the edge! And the sidebar forms a *trapezoid*!
This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...
Wenn „Developer“ den Plain-Text-Teil einer E-Mail „vergessen“ und stattdessen den Rest für Dokumentation missbrauchen, sehen Menschen wie ich, die keine HTML-Mails lesen wollen, und Menschen, die darauf angewiesen sind, oft gar nichts mehr.
Ich merke das auch im Alltag: Vor 20 Jahren war es selbstverständlich, einen Plain-Text-Teil bereitzustellen. Heute denken viele nur noch: „Hat doch eh jeder HTML-Mails.“
Meanwhile the discussion on defining "view"rumbles on: 52 comments · 137 replies
I have largely stayed out of it as I have other more pressing shit to do. 
Interview with Lola Odelola @lolaodelola
"Lola Odelola is a force to be reckoned with. Which is why TetraLogical are delighted to sponsor her work on the W3C Technical Architecture Group (TAG)"
https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/
#Development #Previews
Kelp · A customizable UI library that needs no build step https://ilo.im/164ypi
_____
#Library #HTML #CSS #WebComponents #CDN #WebStandards #WebDev #Frontend
Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci #webdev #webstandards #opensource
Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. #compsci #webdev #wasm #webstandards
What are your favorite blogs about the #web, #webdev, and #webstandards?
(sorry about the hashtags, trying to cast a wider net)
Having had my head in an EAA assessment for the past month i missed this discussion until now
#WCAG #WCAG3 #a11y #WebStandards
Scheduling Approach Alternatives
File encryption with a browser.
I've been exploring the #WebCryptoAPI and I'm impressed!
When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!
I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.
Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo
Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js
Hook Code: https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js
IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.
You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.
YouTube: How about a `<span>` inside the head, and `<link rel=alternative>` inside the body?
HTML5 parsers:
Thanks, I'll take that span as your implied end of `<head>`, and raise you an implied start of `<body>`. Everything that follows is now part of the body.
Context:
https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755
#Development #Trends
The future of browsing the web · ”AI just broke the web that Google built.” https://ilo.im/164cfq
“Chrome’s days are numbered.”
_____
#OpenWeb #WebStandards #AI #AnswerEngine #SearchEngine #Google #Chrome #Browser #WebDev #Frontend
Congrats to editors Matt Garrish and @tzviya for the two newly published @w3c #WebStandards "Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA)" and "Digital Publishing Accessibility API Mappings 1.1 (DPUB-AAM)". #timetoadopt
https://www.w3.org/TR/dpub-aria-1.1/ https://www.w3.org/TR/dpub-aam-1.1/
URLs should be able to include HTTP verbs and headers.
They say "URLs define the "what" not the "how"" but protocol prefixes, file extensions, and query parameters are part of the how and yet they all exist in the URL.
Leaving HTTP verbs and headers out of URLs was an arbitrary decision.
#dokieli ( https://dokie.li/ ) is a web-based #decentralized article #publishing and #annotation #application and browser extension, built as an #opensource ( https://git.dokie.li/ ) project using #webstandards.
dokieli enables individuals and communities to publish, share, and annotate articles using their preferred identities and storage, and you are always free to switch to another application and take your content with you.
ARIA/HTML relationship Severance
"You could use standard HTML controls without all that stinking DOM darkness and encapsulation fandango fucking up your relationships."
#HTML #ARIA #a11y #WebDev #WebStandards
https://html5accessibility.com/stuff/2025/06/07/aria-html-relationship-severence/
the ARIA combobox role has gone through some changes during its specified life. It is worth reading about it in its latest incarnation in ARIA 1.3
W3C Accessibility Specialist Daniel Montalvo will be at the Inclusive Africa Conference 3–5 June 2025.
Daniel’s sessions are available free for remote participants:
- 12.10pm (EAT), 3 June: Global Implementation of Accessibility
- 2.40pm (EAT), 3 June: Roundtable on Developing Africa’s Digital Accessibility Standard
Registration: https://kutanaevents.com/events/inclusive_africa_conference
How strict should the application of "2.5.3: Label in Name" be for languages other than English?
