stevenspriggs 

25 Followers
106 Following
114 Posts
#UX Engineer at #RedHat working with web standards and #WebComponents in #DesignSytems. Based in Morgantown #WV. #WVU alumnus. A #skiing #hiking #climbing #PADI #SDI certified diver and general #outdoors enthusiast.
Twitterhttps://twitter.com/stevenspriggs
Githubhttps://github.com/zeroedin
Personal sitehttps://stevenspriggs.com
It feels only fair that browsers should detect when you're reading the news in a native app and bombard you with notifications telling you how much better the web version is as you try to scroll.
Fair winds and following seas, President Carter. You will be missed. https://www.npr.org/2024/12/29/130189535/jimmy-carter-former-president-dead-at-100

Every single day, I experience someone talking about how hard web development is and how convoluted it is to do anything and how much tooling and effort it takes.

Every single time, they (or someone white knighting the JS industrial complex) say "this is just how it is, front end is just this complicated."

And, my brother in christ, no. You have self-inflicted these wounds. This stuff is HARD, but it does not need to be convoluted. Is is sometimes elaborate, but it doesn't need to be complex.

"Computers lie to us. CSS hides our worst sins. JavaScript covers-up our poor architectural choices. With Lynx, there's no escape. You see the HTML rendered and that's it."

https://shkspr.mobi/blog/2020/12/how-and-why-to-use-lynx-the-faster-web-browser/

How and why to use Lynx - the faster web browser

Lynx is a text based browser. You think the people who browse without JavaScript are weird? Lynx doesn't even do images or CSS! It downloads HTML and renders it at blazing fast speed. If you ever wondered just how slow modern web development has made the web - Lynx will show you the meaning of haste. I use Lynx most days. Not as my exclusive browser - I'm not a masochist - but as a handy tool. If I'm on a bandwidth constrained connection, or a site is overloaded, or I just want to browse…

Terence Eden’s Blog
Oh and if you are interested the fix is in the codepen.
Not a bug, I was just too dense to realize that I needed to account for both the wrapper div, *AS WELL AS* the ::details-content that is now present.

With the update to chrome 131 and the stated styling improvements for details summary.

https://developer.chrome.com/blog/new-in-chrome-131#styling-details

I can no longer use details as display contents in a grid. Works in chrome 130/ Firefox / Safari.

https://codepen.io/zeroedin/pen/vYooZqj

Introduced bug?

@developers

New in Chrome 131  |  Blog  |  Chrome for Developers

Chrome 131 is rolling out now! CSS Highlight Inheritance is changing, more CSS styling for the details element, easier print layout with page margin boxes, and there is plenty more.

Chrome for Developers
Intent to Experiment: Reference Target for Cross-root ARIA

Love design and front-end development? Tired of math? There’s now a simpler approach to *width: 100%* that lets you avoid math entirely: the stretch keyword. Hat tip: Fernando Jorge Mota.

https://fullystacked.net/stretch/ #CSS

The stretch keyword: a better alternative to width: 100% in CSS?

Use margins while avoiding overflow and horizontal scrollbars with width: stretch

Declarative Shadow DOM allows you to create your component's shadow DOM from HTML rather than JavaScript, making server-side rendered components possible.

(bonus: it's now in all browsers, since earlier this year).

A problem we've heard web devs talk about is the inability to share styles though. State of HTML 2023 gave pretty signals on this.

My Microsoft Edge colleagues have solution proposals for this!
➡️ https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ShadowDOM/explainer.md

We'd love your feedback! Feel free to open issue on the repo.

MSEdgeExplainers/ShadowDOM/explainer.md at main · MicrosoftEdge/MSEdgeExplainers

Home for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers

GitHub