swarm-ui: fix specificity claim in AgentTermPreview.css comment
argus's review on PR #4784 caught a wrong technical claim: the comment said the .ui-agent-term-preview-full override rules relied on source order because they had equal specificity to the un-modified rules above. They don't — each override selector adds one more class (the .ui-agent-term-preview-full prefix) than what it overrides, so they're strictly more specific and win regardless of file order. Corrected the comment to say so.
This commit is contained in:
parent
c460e91bd1
commit
7bf4cfbc4c
1 changed files with 5 additions and 5 deletions
|
|
@ -43,11 +43,11 @@
|
||||||
`min-height: 0` is what actually lets the item shrink below its
|
`min-height: 0` is what actually lets the item shrink below its
|
||||||
content's natural height so `.live.terminal`'s own `overflow-y: auto`
|
content's natural height so `.live.terminal`'s own `overflow-y: auto`
|
||||||
(terminal.css) scrolls instead of the whole column growing past its
|
(terminal.css) scrolls instead of the whole column growing past its
|
||||||
container. `!important`-free, but the `max-height: none` overrides
|
container. `!important`-free — the `max-height: none` overrides
|
||||||
below rely on source order (equal specificity to the un-modified
|
below already carry one more class in the selector than the
|
||||||
rules above — same class count on both sides), not on being "more
|
un-modified rules above (`.ui-agent-term-preview-full` prefixing
|
||||||
specific" — keep this block after the un-modified one if this file
|
each), so they're strictly more specific and win regardless of
|
||||||
is ever reordered. */
|
source order. */
|
||||||
.ui-agent-term-preview-full {
|
.ui-agent-term-preview-full {
|
||||||
display: flex;
|
display: flex;
|
||||||
flex-direction: column;
|
flex-direction: column;
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue