From c10e172151d3e8ec508cf1fee7666c8b9d13e2c9 Mon Sep 17 00:00:00 2001 From: Dave Pearson Date: Fri, 14 Oct 2022 09:00:52 +0100 Subject: [PATCH] Markup pseudo-selector as code Other similar items in the surrounding text use code markup, so this feels like it should do too. --- docs/guide/CSS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/CSS.md b/docs/guide/CSS.md index 9c0332bfc..4ca7785c3 100644 --- a/docs/guide/CSS.md +++ b/docs/guide/CSS.md @@ -369,7 +369,7 @@ It is possible that several selectors match a given widget. If the same style is - The selector with the most IDs wins. For instance `#next` beats `.button` and `#dialog #next` beats `#next`. If the selectors have the same number of IDs then move to the next rule. -- The selector with the most class names wins. For instance `.button.success` beats `.success`. For the purposes of specificity, pseudo classes are treated the same as regular class names, so ".button:hover" counts as _2_ class names. If the selectors have the same number of class names then move to the next rule. +- The selector with the most class names wins. For instance `.button.success` beats `.success`. For the purposes of specificity, pseudo classes are treated the same as regular class names, so `.button:hover` counts as _2_ class names. If the selectors have the same number of class names then move to the next rule. - The selector with the most types wins. For instance `Container Button` beats `Button`.