@devongovett I have a habit of throwing things out of the window when I see Limited Availability 😄 But I will definitely try this. Thanks for your answer 🙏
@ryanflorence Not sure if this is what you meant for, but I find libraries supporting asChild/slot pattern (like radix) has easier integration with these kind of components and vice-versa
Chrome DevTools now supports *individual* network request throttling!
Folks have been asking for this for years! DevTools now allows developers to simulate slow network conditions for specific requests rather than the entire page.
This helps in testing how a web application performs and handles issues when specific resources (like images, scripts, or API calls) are slow to load.
⭐️ Small details like this can make a big difference in how a UI feels, and fluid typography is a nice example of how CSS can handle more logic than we often give it credit for.
🤔 It is mostly straightforward to change the font-size of a web page based on the device screen sizes. Media queries can solve this problem.
💡 But sometimes, fixed breakpoints can feel limiting. Font sizes jump at certain widths instead of scaling smoothly.
🧩 It is especially useful for layouts where content should feel balanced whether the screen is slightly bigger or smaller, without sudden visual changes.
📐 Fluid typography solves this by letting text scale continuously based on the screen size. With clamp(), you can define a minimum size, a preferred fluid value, and a maximum size in a single line.
💡 Let's say you need to call a callback prop in a child component when the state of that child changes. The "latest ref pattern" is a useful technique for this case.
👉 Here is a CSS tip in case you need to hide scrollbars on the <body> when a modal is open.
✅ Selecting a parent element based on its children was not possible with pure CSS. But with the :has() pseudo-class, you can select elements based on their children or siblings easily.