What this is

This release fixed the cases where Lens named the wrong rule as the winner. On Tailwind v4 and shadcn sites, a padding or margin diagnosis used to point at a 0px base reset instead of the utility class actually setting the value. Logical properties like padding-inline and margin-block now map to their physical longhands at capture, so the winner you see is the rule the browser is really applying.

The verdict copy got more honest across the board. A visibility:hidden ancestor stopped reporting the display:none “your changes have no effect” message and started getting its own finding with an overridable fix. The “only applies at this screen size” verdict now fires only when the rule actually doesn’t match your current viewport, and the engine stopped presenting any winner the browser’s computed value contradicts.

What it answers

– why does lens show a 0px padding winner on a tailwind site
– how do i find which css rule is actually winning on my page
– why does my element say my changes have no effect when it’s just hidden
– how to fix padding-inline and margin-block not matching the real value
– why does the css override work in one place but not the other

Why we built it

A diagnosis tool is worthless the moment it names the wrong rule. These fixes close the cases where the answer was confidently wrong.