#front-end-engineering

#front-end-engineering

React Native v0.85 introduces a new Shared Animation backend, enhancing the animation capabilities of applications. Upcoming features like <ViewTransition> and Skia Graphite promise to further improve user experiences.

Using such a resolution in the web browser would render a tiny illegible desktop site. To avoid that, CSS pixels add a layer of abstraction. Initially the amount of actual pixels compared to CSS pixels was simply a 2x or 3x conversion, but these days fractional scaling is also common.

YouTube iframes can be pretty heavy, leading to a noticeable hit on load time and Core Web Vitals, especially LCP and CLS.

Google credits security researcher Shaheen Fazim with reporting the exploit to Google. The dude's LinkedIn says he's a professional bug hunter, and I'd say he deserves the highest possible bug bounty for finding something that a government agency is saying "in CSS in Google Chrome before 145.0.7632.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page."

Frontends are no longer written only for humans. AI tools now actively work inside our codebases. They generate components, suggest refactors, and extend functionality through agents embedded in IDEs like Cursor and Antigravity. These tools aren't just assistants. They participate in development, and they amplify whatever your architecture already gets right or wrong. When boundaries are unclear, AI introduces inconsistencies that compound over time, turning small flaws into brittle systems with real maintenance costs.

Browser cache - Sometimes the browser is still loading the old CSS file. A hard refresh (Ctrl + F5) usually fixes it. Wrong file linked - Double-check if your HTML is actually linked to the correct CSS file. Specificity issues - Another CSS rule might be overriding your changes.

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.

WCAG is not normatively stating focus must be trapped within a dialog. Rather, the normative WCAG spec makes zero mention of requirements for focus behavior in a dialog. The informative 2.4.3 focus order understanding doc does talk about limiting focus behavior within a dialog - but again, this is in the context of a scripted custom dialog and was written long before inert or <dialog> were widely available.

Can you formulate the css code to apply the glassmorphism (GM) effect b/g to the tasks below: Glassmorphism code snippet background: rgba(255, 255, 255, 0.2); backdrop-filter: blur(5px); border: 1px solid rgba(255, 255, 255, 0.1); 1.1 Apply the GM effect to the Share B/G, Gallery B/G &amp; Vid B/G icons during onmouseout. 1.2 Apply the GM effect to the Social icons pop-up panel B/G during onmousehover on the Share icon.

Everything you need to know in development &amp; design this week, rounded up for you (Week 4, 2026). You'll find the most essential things right now: JavaScript &amp; CSS libraries, useful code snippets, crucial web dev news &amp; resources, curated AI tools, free design assets, and plenty of other good stuff we found! Highlights: 2026 Tech Stack Refresh! Dive into updated &quot;Top 10&quot; lists for Off-canvas menus, responsive dropdowns, fullscreen navs, and more to get your projects ready for the year ahead.

Chris Coyier demonstrates how to maintain a video's state across different pages using CSS view transitions. He notes that this is fairly easy to do with same-page view transitions, but with multi-page view transitions you'll need to leverage JavaScript's pageswap event to save information about the video's state in sessionStorage as a JSON string (works with audio and iframes too), and then use that information to restore the state on pagereveal. Yes, there's a tiiiiny bit of audio stutter because we're technically faking it, but it's still super neat.

Support is limited to Chrome only because this technique uses recently released features, including corner-shape, sibling-index(), and unit division. In this article, we will explore another type of grid: a pyramidal one. We are still working with hexagon shapes, but a different organization of the elements. A demo worth a thousand words: For better visualization, open the full-page view of the demo to see the pyramidal structure. On screen resize, you get a responsive behavior where the bottom part starts to behave similarly to the grid we created in the previous article!

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).