Skip to content
install

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

diagnostic · one of 29free, no counter

Cascade

Which CSS rule is actually winning?

A style that "does not apply" almost always applies and is then beaten. The browser shows you the winner with the losers struck through, one element at a time, which answers what happened but not how often it happens. This reads the cascade across the page and ranks where it is doing the most work.

Reach itPress +K on any tab and type cascade.Ctrl+Kon Windows and Linux

Which rule wins, drawn on the page as a heatmap
readsmatched rules per element
writesnothing
sendsnothing
flags!important, inline styles
sortsspecificity, then order
overlayheatmap on the page
planfree
Add LoupeKit- opens the list of browsers it can be installed in

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

in the panel · free, no counter

section#about

What this actually is

When a change has no visible effect and the element looks right in the inspector, and before a refactor that will move selectors around - a sheet with a lot of `!important` breaks differently from one without it, and it is worth knowing which you have.

section#reference

What beats what

origin and layer
user agent, then author layers in declaration order, then unlayered author styles
!important
inverts the origin order entirely - an important user-agent rule beats everything you write
inline style
a specificity nothing in a stylesheet can reach without !important
specificity
ids, then classes and attributes and pseudo-classes, then elements
source order
the last one wins, and this is the only tie-break left
section#asked

Asked about this diagnostic

How is this different from the Styles pane in DevTools?

That pane answers for one element after you have found it. This tints the whole page by how contested it is, so you find the component that needs looking at before you know which element to click.

Does it understand cascade layers?

Yes, and layers change the answer more than specificity does - a low-specificity rule in a later layer beats a high-specificity rule in an earlier one, which is exactly the case that looks like a browser bug.

Why does it show rules that did not apply?

Because that is the question being asked. "Which rule wins" is already answered by the page in front of you; what you came for is why the one you wrote is not it.

Add LoupeKit- opens the list of browsers it can be installed in

TWO BUILDS9 browsers

Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome build

63 of these · no host permissions · three free audits