#css-specificity

#css-specificity

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.

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

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.

Stacking contexts are incredibly useful, but they're also widely misunderstood and often mistakenly created, leading to a slew of layout issues that can be tricky to solve. Have you ever set z-index: 99999 on an element in your CSS, and it doesn't come out on top of other elements? A value that large should easily place that element visually on top of anything else, assuming all the different elements are set at either a lower value or not set at all.

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.

Teams often use customer and user interchangeably until it breaks alignment. Here's how separating the two clarifies research, prioritization, and messaging across B2C, B2B, and B2B2C products.

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.

@keyframes animations can be named using strings, allowing syntax like @keyframes "@animation" { /* ... */ } with corresponding animation: "@animation" declarations. This capability has existed for 11 years across browsers, yet remains relatively unknown to many developers seeking alternative keyframe naming conventions beyond standard identifier formats.

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.

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.

Welcome to The CSS Selection 2026! In this article we're having a look at how CSS is used at scale on over 100,000 websites. We'll look at what things are common on most websites and discover interesting outliers. This is the first edition of what I hope to be many, so this is meant as a baseline for future editions, setting up the first numbers to compare with in coming years.

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!

Anytime an exciting new web technology starts to land in browsers, developers want to know "when in the world am I going to be able to use this?" Currently, the finalized syntax for Grid Lanes is available in Safari Technology Preview. Edge, Chrome and Firefox have all made significant progress on their implementations, so it's going to arrive sooner than you think. Plus, you can start using it as soon as you want to with progressive enhancement.

There have been a few drafts of a specification function for this functionality, most recently, contrast-color() (formerly color-contrast()) in the CSS Color Module Level 5 draft. But with Safari and Firefox being the only browsers that have implemented it so far, the final version of this functionality is likely still a ways off. There has been a lot of functionality added to CSS in the meantime; enough that I wanted to see whether we could implement it in a cross-browser friendly way today. Here's what I have: color: oklch(from &lt;your color&gt; round(1.21 - L) 0 0);

As a contracting front-end developer and Design Systems consultant, I don't always get to work on new things. Sometimes I work within codebases. Sometimes alongside them. Sometimes these codebases are years and years old. When you dive into these projects, you're not just reading code, you're excavating years of decisions, technological limitations, and creative workarounds from days gone by. Over the last decade, I've called this Front-End Archaeology.

After searching and searching, it seems that you and I are the only ones in the world who have this problem. In the F12 console, I found: SEC7113 "CSS was ignored due to mime type mismatch". Discussion here: MSDN. It seems that IE9 and above "sniff" the HTTP headers for the correct MIME type, and ignore JS and CSS that have the wrong header. When it fetches files from the local filesystem, it should disable this sniffing, since there aren't any real HTTP headers. But our two computers, (and nobody else's) are sniffing and ignoring headers.