Heading out from #CSSDay with a new take on mixins, inspired by @kizu's talk and experiments. Have to write up my thoughts, but in brief: How do you un-mix something, once it's been mixed in?
@kizu Yeah, I think that's generally true. But I'm curious if there are places where it helps for a mixin use to 'cascade' with itself. If applied on two overlapping selectors with different arguments, is it sometimes useful for one mixin call to 'win' entirely rather than each resulting property being compared individually.
@mia Hm hm, yep, I can see something like that, where some mixin could result in two sets of declarations which might not play well together, and where you could want to only every apply one of them.
It was lovely meeting so many of you at #CSSDay! I had a great time. Now off to Spain for CSSWG, and then running a #CSS layout workshop at the end of June.
(use the conference hashtag in allcaps for a 10% discount!)
"Here's a cool thing, please don't use it" @rachelandrew talking about the problems with auto-layout (grids/masonry) without fixes for reading order. #CSSDay
The man she's with is watching Mission Impossible and keeps saying "oh no. oh no. oh no."
I'm also watching MI, and pausing regularly to get a photo of whatever antics men are up to [in brackets]. Not pretending like I'm the normal one here.
Ok, most of these images still need alt text and captions. I can't do all 500+ at once. But at least I have a system (and a way for people to help out)! Thanks #eleventy
Many teams are still using decade-old approaches and third-party tools for #CSS layout. That's not just extra work, but will leave you with less reliable results.
Join my new Cascading Layouts online workshop at the end of June!