#oninput

#oninput

The query_one() method throughout the Textual documentation allows users to retrieve a single widget that matches a CSS selector or a widget type. You can pass in up to two parameters to query_one(), which are the CSS selector and the widget type, or both at the same time.

TanStack RSCs are supported through three primitive APIs that allow manipulation of RSCs as any other stream of data, compatible with tools like React Query and TanStack Router.

Events are essential inputs to modern front-end systems. But when we mistake reactions for architecture, complexity quietly multiplies. Over time, many front-end architectures have come to resemble chains of reactions rather than models of structure. The result is systems that are expressive, but increasingly difficult to reason about.

When applications grow, state becomes messy, components break, and small changes ripple into unexpected bugs. This is where many learners realize that knowing React syntax is not the same as knowing how React applications are built.

Hi everyone! This week, we saw a lot of activity on X about the new AI skills system. Personally, what excited me most is the new Firefox release that unlocks interesting things for React developers. The React Native ecosystem is also super active, with many interesting releases. And I'm sure Expo 55 beta will drop just after we send our email 😅, so make sure to check their blog because it's coming soon. Don't miss the next email! As always, thanks for supporting us on your favorite platform:

Ana proposed the following: Is this enough in 2026? As an occasional purveyor of the visually-hidden class myself, the question wriggled its way into my brain. I felt compelled to investigate the whole ordeal. Spoiler: I do not have a satisfactory yes-or-no answer, but I do have a wall of text!

By how much? Well, that would depend on the value of the <length> argument provided. Thomas Walichiewicz, who proposed :near(), suggests that it works like this: button:near(3rem) { /* Pointer is within 3rem of the button */ } For those wondering, yes, we can use the Pythagorean theorem to measure the straight-line distance between two elements using JavaScript ("Euclidean distance" is the mathematical term), so I imagine that's what would be used behind the scenes here.

Every embedded video comes with a real cost to page load performance. Each player loads extra resources, whether the user ever hits play or not, as Chris Coyier noted in his blog post on "YouTube Embeds are Bananas Heavy and it's Fixable". The approach of using in that article works well when the video appears further down on the page and loads outside of the initial viewport. If the video is directly in the initial viewport, it can still cause a cumulative layout shift (CLS).