When seeing a border described as "circle() square()", do you imagine is as:
- A circle surrounding a square (outside-in)
- A circle surrounded by a square (inside-out)
See first comment for illustration
An issue we're really eager to tackle in the web platform very soon is this thing where state is reset when an element is being reparented/moved (iframes reloading, focus/selection clears, animations restart).
Does anyone else care about this?
Speak up! Share your pain!
One thing I don't see in #webperf traces as much as before: framework overhead. I think frameworks really matured in the last few years in terms of performance.
One thing I do see often enough: layout thrashing in 3p libraries (think chart libs, animation libs etc).
If you're adding view transitions to your sites, the Material Design guides have some great examples, and some patterns to avoid. I don't think their word is law, but there are a lot of good ideas here.
https://m3.material.io/styles/motion/transitions/applying-transitions
A new #webperf blog post: about performance.timeOrigin and clock drift
https://dev.to/noamr/when-a-millisecond-is-not-a-millisecond-3h6
Going to start involuntary nodding into the late 2030s whenever the memory of this post percolates from the depths:
https://www.spicyweb.dev/the-great-gaslighting-of-the-js-age/
/by @jaredwhite
IntentToShip
Jake Archibald
Alex Russell
Andrea Junker 