I've been caught by this before, and I've seen other experienced #CSS devs get stuck on it:
* { color: deepPink; }
html#high-specificity { color: teal !important; }
If we put that ID on the root, and some text in our document, what color will the text be?
I built a visual explainer of the CSS Cascade, the algorithm that determines the "winning value" from a list of competing declarations.
It's built on work by @bram.us and @miriam.codes.
cascade.arpit.codes
I wrote about how it came together on my blog: arpit.blog/notes/2026/0...
The Jetsons lied to us
The CloseWatcher API landed in Firefox 149, making it easy to listen for platform-specific 'dismiss' signals. Here's how it works:
The recording of @kitation.co.uk talk ‘The Plateau of Accessibility Compliance: Where do we go from here?’ is now available to watch online!
2026.stateofthebrowser.com/speaker/chad...
A screenshot of the video section of the HTML standard, now containing the loading attribute, a new addition
Spec proposal merged.
HTML video and audio lazy loading is now a web standard.
github.com/whatwg/html/...
html.spec.whatwg.org#the-video-el...
html.spec.whatwg.org#the-audio-el...
@beyondtellerrand.com Hi Marc, I'd love to attend #btconf Düsseldorf remotely via a streaming pass. Does the scholarship form also cover streaming passes, or is that only for in-person tickets?
So much so that I feel the urge to redesign my portfolio based on the approach he showed. For now, I’ll dive into his UA+ stylesheet and oli.css project to get a deeper understanding.
fokus.dev/tools/uaplus/
olicss.com
Many of the speakers were kind enough to share a link to their slides. I haven’t checked out all of them yet, but I liked @matuzo.at’s talk ‘Breaking with habits’.
noti.st/matuzo/K64nm...
By all accounts, it was an excellent event. The regret at missing out (RAMO) is real. I remotely attended #SotB 2026 and I’d love it if more events offered a remote option.
adactio.com/journal/22353
I couldn’t make it to #WebDayOut. Thankfully, @adactio.com wrote about it and linked to a bunch of online talk about it. Special shout out to @joshtumath.uk who live-blogged each talk.
adactio.com/journal/22465
Thank you. I've added a comment with a test case.
😂😂😂
Thanks Roma!
Also, your anchored sidenotes implementation is excellent, I learned a lot from it.
I came across this bug while exploring @kizu.dev's implementation of Eric Meyer's Nuclear Anchored Sidenotes.
codepen.io/kizu/pen/abR...
@jensimmons.bsky.social Hi Jen, I think I found a bug with CSS anchor positioning in Safari. I have a chain of elements where each one positions itself below the previous one using `inset` and `anchor()`. It works as expected in Chrome & Firefox but breaks in Safari.
Pen: codepen.io/editor/arpit...
Especially when `@scope` rules are written as inline styles inside a `<style>` element in the HTML. Chris Coyier called these "kinda like Shadow DOM without using the Shadow DOM" in his CSS Day talk.
frontendmasters.com/blog/scope-i...
Miriam showed a similar technique using an `end-scope` attribute as a selector to reset the inherited properties. Unfortunately, I don't think CSS gives us a better option right now. Turning off inheritance is not an easy task.
youtube.com/watch?v=T-X6...
Today I learned that when using the new CSS `@scope` rule, inherited properties leak through the donut scope.
I wrote more about it on my blog.
arpit.blog/articles/202...
So. Anchor Positioning and DevTools …
I sat together with The Hype™ tonight and this is what we built in 2 hours.
Main takeaway from this experiment is that it still requires a “Subject Matter Expert” (in this case: me) to build this, instructing The Hype™ what to do (and sometimes how to do it).
Finding the containing block is *super easy* in @Polypane.app, which literally just lists it for each element in the Elements panel.
Along with the offsetParent and the stacking context parent, two other important concepts that often confuse devs
Way too many developers are sleeping on Polypane ;)
Wow! I had no idea Polypane did this. I am already a fan of the responsive design view.
In the video, @tabatkins.com mentions that dev tools really need a way to show the containing block for elements, especially absPos/fixedPos elements.
Paging @bram.us, @una.im, @jakearchibald.com and @jensimmons.bsky.social.
It would be super helpful to visualise what the containing block is.
I also saw the Winging It episode on ‘Debugging CSS Anchor Positioning‘. It really helped me develop a mental model of how anchor positioning works under the hood and why the gotchas exist.
www.youtube.com/watch?v=3vwr...
Oh boy! I had no idea anchor positioning was this complicated. I would be afraid to touch it if not for this recommendation from James Stuckey Weber to make it work reliably.
1. Make the anchor and the positioned element siblings.
2. Put the anchor first in the DOM.
www.oddbird.net/2025/01/29/a...
🎉 new blogpost 🎉
Un-Sass'ing My CSS: Native CSS Nesting
Nesting was a dream feature in Sass and it's recently become 'native' in CSS.
This post covers syntax, specificity, real patterns, and the key differences you need to know.
www.alwaystwisted.com/articles/UnS...
#CSS #Sass #FrontEnd #WebDev
Agreed! It did feel a bit hacky.
Hey @kevinpowell.co, I liked your video on the slide-in nav of your website. I recreated the slide-in effect using the upcoming CSS scroll *triggered* animations and blogged about it on my website.
Post: arpit.blog/notes/2026/0...
CodePen demo: codepen.io/editor/arpit...
Embracing progressive enhancement can make it much easier to adopt newer web features.
