I’m excited to share a new project from Adobe Spectrum Web Eng that tracks support for #CSS features within and across the shadow DOM.
The goal is to provide visibility into feature parity and outstanding issues. We hope you find it useful - open to contributions!
shadow-dom-css.adobe.com
That's new. I couldn't make an online purchase until I turned on all my content blockers (including those via a VPN service)
Excellent work!
Want to learn all about web components this week? My 8-hour online course, Web Components Demystified, is on sale for $10 through March 13th. Use the code JUST10
scottjehl.com/learn/webcom...
there ARE a couple really big gotchas to be aware of, nice recap from @chriscoyier.net here
JavaScript Iterator․zip landed in Firefox 148, making it simple to loop over multiple things at the same time. Here's how it works:
This is indeed very nice. 🚀 Media Queries have been around for what seems like forever. So I still have some muscle memory pushing on their placement. 😅
*web frameworks klaxon*
If you work on a web framework then there is a w3c proposed community group: the Web Frameworks Community Group, a place for framework folk to feedback to browser vendors about what they want to see!
If you want this it needs your support!
www.w3.org/community/gr...
Thanks. I’ll take a look.
Do you have ideas about what kind of default lint rules a css linter should check by default? I'd love to hear ideas in github.com/csskit/csski....
Well, how it haunts me. 😅
Also there are some usability issues like the user needing to explicitly close the menus. But in of itself not a deal breaker. The demo shows a simplified navigation setup is possible and with minimal hydration issues with third-party libraries like React.
It is accessible. However, the 'more' button, for example, could do with a bit more detail to make clear what's going on.
Made chicken rice for lunch. Turned out great. However, afterwards I decided to add some chilli crisp. Do I get pulled in front of a rice abuse tribunal?
Do you want a dynamic, responsive navigation?
What if you want zero config, no DOM manipulation, no attributes popping up?
Well, slot assignment, popovers, and anchor positioning, you can get it done. Okay, that's a lot. But, doable.
#CSS #webcomponents #customelements
codepen.io/dutchcelt/fu...
The inaugural edition of The CSS Selection is out! Super interesting look into how the top 100k sites use CSS.
I very happily sponsored Barts work on this, go check it out!
My contract is ending at the end of February and so I’d like to find a new role ASAP.
I am a senior-level design systems developer / design technologist / front-of-the-frontend developer that specializes in web accessibility.
I work remotely from my home in Winnipeg, Canada. 🇨🇦
Shares appreciated!
One team was using our components and was experiencing FOUC, so I suggested this tip. The app rendered faster. Not just perceptively but actually.
Many apps have a number of rerenders / repaints when first landing. This trick helps the browser skip all that.
Yep, I do this on a number of projects. Still waiting for folks to complain.
I also have it running on my blog.
Firefox 147 rolled out some cool stuff. This has to be my fav. Hey, Safari, hot potato!
Understanding the fundamentals of CSS layout
When devs say that CSS is hard, they're usually talking about CSS layout. What often gets omitted is that developers are assumed to understand and effectively use CSS without being taught how it works in the first place.
polypane.app/blog/underst...
😲
Pretty much any codebase that I've worked on that uses CSS Modules (not to be confused with the web platform feature, CSS module scripts) will typically create a class for each element being styled, then import that class name, and apply it to the element being styled.
If you are reducing your IT costs through deskilling front-end you should put a Design System on the top of your shopping list.
Deskilling doesn't mean you can do without front-end, it means being more effective and efficient by hiring the people you need and get the most out of that investment.
Yes, I like this. A shame they don't render it on the element itself. Now you need to align on a usage pattern to apply these custom properties.
As I work mostly with Custom Elements I could see doing something similar and add them to a constructed stylesheet in the shadowRoot.
pfft. jetlag is kicking in.
A business model based on ad revenue for a content website is problematic. Especially when the content can't be protected. Or at least has no legal recourse to protect its unique content or IP.
Tailwind may need to go non-profit.
Indeed. It can be tricky to recognize the difference until you start to consider sharing system tools/libraries.
Being transparent and open/inner sourcing has, as always, been a good foundation for a system to grow and adapt, because communication lines are short and awareness is greater.
