Skip to content

Commit 05d59a6

Browse files
authored
machines: Fix CSS rule specificity when overwriting PF4 rules
PF4 imports come first, then we import the custom CSS. In SCSS the most recent rule should take effect, when there is not difference in the specificity. Seems that the ordering of the bundled CSS is not very consistent however. When being certain about overwriting default value, increase the specificity, so that we don't rely on the order of the imported CSS. Closes cockpit-project#14965
1 parent 1922127 commit 05d59a6

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

pkg/machines/components/stateIcon.scss

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,6 @@
1616
}
1717
}
1818

19-
.resource-state--shut-off, .resource-state--inactive {
19+
.pf-c-label.resource-state--shut-off, .pf-c-label.resource-state--inactive {
2020
background: transparent;
2121
}

pkg/machines/components/vm/vmExpandedContent.scss

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
margin-top: 2rem;
3232
}
3333

34-
.ct-vm-overview {
34+
.pf-l-gallery.ct-vm-overview {
3535
$ctVmBreakpoint: 1000px;
3636

3737
@media screen and (max-width: $ctVmBreakpoint) {

0 commit comments

Comments
 (0)