I’ve wanted to use it with the trig functions to calculate an angle for a rotation.
Posts by James Stuckey Weber
The new tool should be cheaper than the one it replaces. 2 It should be at least as small in scale as the one it replaces. 3 It should do work that is clearly and demonstrably better than the one it replaces. 4 It should use less energy than the one it replaces. 5 If possible, it should use some form of solar energy, such as that of the body. 6 It should be repairable by a person of ordinary intelligence, provided that he or she has the necessary tools. 7 It should be purchasable and repairable as near to home as possible. 8 It should come from a small, privately owned shop or store that will take it back for maintenance and repair. 9 It should not replace or disrupt anything good that already exists, and this includes family and community relationships.
finally, Wendell Berry's standards for technological innovation--truly as relevant now as they were in 1987 #othernetworks
Today I published the second update of this month to the Practical Accessibility course content.
I have at least two or three more updates coming this April.
As I promised, I want to keep the course as up-to-date and as relevant to your work as possible.
Get access @ practical-accessibility.today
Anchor Positioning in Space | A comprehensive guide and playground for CSS Anchor Positioning | anchor-positioning-in-space.schalkneethling.com #css
I had been ignoring a needed migration off of Worpress for... checks notes... 7 years. Thanks to @zachleat.com for the tools that made it happen in an hour.
Winging It live stream on Thursday with @jamessw.com and @stacykvernmo.com to explore some hidden gems of UI development—from @starting-style for smoother entry transitions to AVIF images and using the browser’s built-in lazy-loading. join us!
www.youtube.com/live/XOm3vEJ...
I've seen this exact use case before, and think it's worth opening an issue on CSSWG, especially if you have thoughts on how to take scroll into account on multiple elements.
That said, the spec was written alongside the Chromium implementation and likely includes Chromium-specific limitations and work arounds. So with more implementations, adjustment is needed?
So it isn't the sticky position that is being ignored, it's the scroll offset of the sticky element. If you make that the default anchor, it ignores the other element's scroll offset.
There's an example here that shows an anchored element on multiple scroll containers only following one scroll.
If the size is derived from a non-default anchor, the size shouldn't update. The algorithm is essentially: 1. Resolve all the anchors to position and size the element. 2. When the default anchor scrolls, offset the position the same amount.
I'm pretty sure Chrome is correct per the spec. The anchored element can only follow the scroll offset of a single anchoring element, which is determined by the default anchor (the `position-anchor` here).
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...
I spent too much time looking at too many colo(u)rs to try and optimise them for csskit. Here are some interesting findings.
www.keithcirkel.co.uk/too-much-col...
For those who want to test their perception of colour, I made a little game called "What's My JND"
www.keithcirkel.co.uk/whats-my-jnd...
One day you're like "we should send a weekly newsletter about the cool stuff on @codepen.io and around".
Then 500 weeks go by. 🎉
codepen.io/spark/500
Tools also avoid rounding to prevent color shifts if you convert between spaces repeatedly, so they likely preserve more than is needed.
Thank you for doing the math! I'm curious if that holds up across channels? I'm guessing some color spaces would also show more differences in some hues?
Or perhaps nuance isn't really needed here... 3 is sufficient, and likely more than sufficient, and 4 is never needed?
Explore Container Queries with @miriam.codes in the context of the delicious Baseline Bakery. Donuts & #CSS? Yum!
www.oddbird.net/2026/02/18/q...
Shared in the February issue of OddNews:
us19.campaign-archive.com?u=80219aa68d...
You can find the slides of my #SotB2026 talk on my blog: www.bram.us/2026/02/28/a...
Played around with a polyfill for Element.matchContainer() and it works! Just needed to tweak the polyfill with a @starting-style. codepen.io/jamessw/pen/...
Looking forward to the "State of" trench coat to replace the t-shirts next year.
💡 CSS Tip!
For years, we've had the "z-index, stacking context" nightmare, but we will soon have a worse nightmare related to Anchor Positioning 😱
When it doesn't work, it's frustrating, so it's time to learn how it really works.
css-tip.com/anchor-issues/
It's not as simple as you might think!
That seems like a very reasonable thing to want, but not sure how to do that without causing cycles.
I haven’t played with Container Queries for anchors much yet, but my understanding is no.
Tomorrow on Winging It (live) I'll be chatting with @stacykvernmo.com & @jamessw.com about my approach to responsive type in #CSS – without third-party calculators or complex unit conversions – and some of the research I did to get there.
Join us at 10am PT/1pm ET!
www.youtube.com/live/B-r6wem...
It was too icy to run, so instead I wrote a blog post. Some thoughts about the new problems generative AI introduces in the content operations pipeline, and why my spidey-sense for plagiarism is broken rachelandrew.co.uk/archives/202...
Here are a few things I plan to cover in the Poetic #CSS course, but I'd love your input and questions! Where are you having the most issues, what piques your curiosity, and where do you have questions?
Feel free to vote for multiple in the replies, or suggest other topics & specific questions.