Excited for this talk by @argyleink.
I got a sneak peek yesterday, and this is gonna be gooooodddd! 🤩
Excited for this talk by @argyleink.
I got a sneak peek yesterday, and this is gonna be gooooodddd! 🤩
Here's that issue about overscroll areas that @Una just mentioned.
https://github.com/openui/open-ui/issues/1457
I feel like they should probably be defined in CSS. See the issue for my reasoning here.
@nomster We want your feedback! Write a blogpost, send me a message, etc.
Very eager to hear what your use cases and needs are here 😊
At #CSSDay, we (@nomster and I) did a first public pitch of something we are currently prototyping: a way to add styles based on the active navigation.
Handy for View Transitions, and a few other things.
https://drafts.csswg.org/css-navigation-1/ is a WIP spec, with some bits implemented (behind a flag) in Chrome.
There, I fixed it:
:root {
--masonry: grid-lanes;
}
.container {
display: var(--masonry);
}
YES, Dark Mode Toggles _should_ be a browser feature.
I wrote about this before: https://brm.us/dark-mode-override
Find the link to the Chrome Bug in the post, and hit the star next to it to "upvote" the bug.
If you liked Jelle's talk and want to revisit, I have a small section on value processing on my blog (as part of a post on IACVT): https://brm.us/value-processing
CSS Day, day 1. #cssday
CSS DevRel, The Reunion. #CSSDay #ChromeDevRel
Caption: @argyleink, @Una, and I.
Dropped my stuff off at the #cssday venue. Like you do. Totally normal.
A PSA for the #cssday attendees:
It is perfectly safe to attend this year. Left my CSS Flamethrower at home. Apparently they don’t want me to burn the venue down.
But no worries. I am only bringing an oscilloscope - it been repaired since it exploded last year - and lasers. Perfectly safe.
On my way to #cssday, having a stop with some coffee and working on finishing my demos. What can go wrong. Totally prepared. Like a professional.
#cssday, day 0.
Tomorrow's gonna be a day of travelling + some meetings at the NL office + setting up our booth at the venue + pre-conf speaker dinner + a final rehearsal (and some last minute changes to the deck)
On Thursday the it's showtime 🤩 #cssday
Ready for this! #cssday
Anyway... the talk is done. Rehearsed a couple of times. Happy with the pace and I still have 10 - 15 minutes left for the demos that I have planned and Q&A.
Panic over.
RE: https://front-end.social/@html5test/116686493760532281
Every time I decide to write a talk I underestimate the time I need. I do have a rough idea, but there is this whole period of me just making random slides. Sometimes weeks.
Then suddenly I am happy. Build the rest of the talk in a day or two. Way too long. Cut in half. And it just fits together.
I haven't yet made plans for speaking at conferences this fall – limited time and writing another talk kind of felt too much...
Now that the CSS Day talk is ready, I really think the CSS DOOM chapter would work really well as a standalone talk.
Hit me up in my DMs – love to talk about CSS DOOM
This weekend was full-panic mode for #cssday as I had not a single slide or even an outline. And the conference is next week.
It took a couple of days, but last night I finished it and thought I could relax again.
Did a full run-through today and I’m about 15 minutes long. Back to panic mode.