From 92c354e82e9cb1aee78c27f3727a9ebef72fac4e Mon Sep 17 00:00:00 2001 From: hbhalodia Date: Mon, 31 Aug 2026 14:21:55 +0530 Subject: [PATCH] Fix the zebra stripping for privacy policy tables for users data --- src/wp-admin/css/forms.css | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/src/wp-admin/css/forms.css b/src/wp-admin/css/forms.css index f7e6accfce0fd..c89f66863ba0a 100644 --- a/src/wp-admin/css/forms.css +++ b/src/wp-admin/css/forms.css @@ -1490,12 +1490,11 @@ table.form-table td .updated p { .privacy_requests thead td:first-child, .privacy_requests tfoot td:first-child { - border-left: 4px solid #fff; + border-left: 4px solid transparent; } .privacy_requests tbody td.check-column { - border-left: 4px solid #fff; - background: #fff; + border-left: 4px solid transparent; box-shadow: inset 0 -1px 0 rgba(0, 0, 0, 0.1); } @@ -1517,7 +1516,6 @@ table.form-table td .updated p { .privacy_requests tbody td:not(.check-column), .privacy_requests tbody th { - background: #fff; box-shadow: inset 0 -1px 0 rgba(0, 0, 0, 0.1); } @@ -1525,18 +1523,26 @@ table.form-table td .updated p { box-shadow: none; } +/* + * The results row is injected after its request row by privacy-tools.js, so the + * two rows fall on opposite sides of the zebra striping. Give the pair a single + * shared background so an expanded request still reads as one unit. + */ +.privacy_requests tbody tr.has-request-results > *, +.privacy_requests tbody tr.request-results > * { + background-color: #fff; +} + .privacy_requests .next_steps .button { word-wrap: break-word; white-space: normal; } .privacy_requests tr.status-request-confirmed td.check-column { - background-color: #fff; border-left-color: #3858e9; } .privacy_requests tr.status-request-failed td.check-column { - background-color: #f6f7f7; border-left-color: #cc1818; }