WCEU23 – Day 2

My second day of the main conference part of WordCamp Europe 2023 was hampered slightly by a late start on my part.

Dan, sweating, with an actively-used dancefloor in the background.
I can’t say for certain why I woke up mildly hungover and with sore knees, but I make an educated guess that it might be related to the Pride party I found myself at last night.

Still, I managed to get to all the things I’d earmarked for my attention, including:


×

3 comments

  1. @dan great write up. Thanks for sharing.

    Read more →

  2. @dan, thanks for the review!

    I hope I have stepped into your post before. Thanks for sharing your experience around the event. I hope to see you in Turin, and we can chat about CSS.

    The point about Safari on old devices is a big problem. I had issues using dynamic viewport units. A few months after the WordCamp, a client had a classroom with old 40 iPads that stopped receiving updates.

    Following up with some items:
    – Baseline 2023 was released: https://web.dev/blog/baseline2023
    – @layers has two threads to discuss; bring it to the core: https://github.com/WordPress/gutenberg/issues/51128
    – Now you can see the baseline flags on “Can I use”
    – :has() now is available on Firefox since version 121
    – Nesting now is available on Firefox since version 117
    – Clamp is super handy for fluid text and images. For me, the benefit is having more clean code
    – Container queries need a talk by itself, but there is a nice video from Una that covers the importance of it https://www.youtube.com/watch?v=gCNMyYr7F6w

    1. Dan Q Dan Q says:

      Thanks! Yes, I should be at WCEU 2024!

      I’ve become a big fan of container queries – I’ve used them for example on the homepage of this site to support in inner layout of the dynamically-sized/positioned “grid” of post tiles. I was already using clamp for fluid type-sizing. Super glad that :has finally enjoys support in Fx though!

Reply here

Your email address will not be published. Required fields are marked *

Reply on your own site

Reply elsewhere

You can reply to this post on Mastodon (@dan@danq.me), LinkedIn, Facebook.

Reply by email

I'd love to hear what you think. Send an email to b21450@danq.me; be sure to let me know if you're happy for your comment to appear on the Web!