Phil Wolstenholme

The inaugural #StateOfHTML 2023 Survey has launched!

Read my blog post for background:
https://lea.verou.me/blog/2023/state-of-html-2023/

Or take the survey directly: https://survey.devographics.com/en-US/survey/state-of-html/2023/?source=leaverou

If you currently use #docker with Docker Desktop or Colima on the Mac for #craftcms projects, definitely check out @OrbStack

It's a drop-in zero config replacement that still uses Docker… but it's significantly faster, and uses less much less energy. https://orbstack.dev/

It's not perfect and needs more testing with different input types, but I'm pretty pleased with this use of a relatively small amount of JavaScript paired with a scroll driven animation to make a 'sticky only when scrolling up' header that feels native-esque and nicer than just watching the scroll direction and flinging a fixed speed translateY transition on the header:

https://codepen.io/philwolstenholme/full/MWZOGrx

Never in my life would I expected a cybersecurity issue (at least not a non-food safety issue) to result in a food recall

Add this to your risk assessments

Happy Badger-Mushroom-Versary! #weeblsstuff

I forgot about CSS Naked Day (https://css-naked-day.github.io) this year, but there's always a link in my personal site's footer to https://wolstenhol-no-css.philgw.workers.dev which is a version of my site with all the CSS removed.

👋 I'm back with a somewhat compiled list of research on which input types are accessible.

🔗 https://www.ellyloel.com/garden/input-types-a11y/

Thanks @hi_mayank for suggesting I should put it together! Definitely helped me get over the imposter syndrome of not thinking I was the right person to put together a list like this 😅

As mentioned in the post, feedback is welcome, I want to make the list as "correct" as possible.

#A11y #Accessibility :a11y:

Goodness gracious this is well written:

https://johan.hal.se/wrote/2023/02/17/what-to-expect-from-your-framework/

Does anyone have a nice method of feature detecting CSS cascade layer support? I have a fun idea of using the Postcss polyfill to create a polyfilled (but verbose) fallback CSS file, and the original CSS file with @layer. In a non-polyfilled bit of CSS I'll use background-image inside a layer (so browsers without support ignore it) to make a HTTP request that sets a cookie. Then, in subsequent page loads, an edge function will read the cookie and swap out the polyfilled file for the original.