/**
 * The diagnostics table and the Professional row badge of the options page.
 *
 * Loaded only on `options-general.php?page=blocks-product-editor-for-woocommerce`
 * (`Modules\DiagnosticsModule::enqueue()`), so nothing here leaks into the rest
 * of the admin.
 *
 * **The colour is an addition to a word, never the message.**
 * `Views\Admin\Diagnostics` prints OK / WARNING / MISSING, and the page is read
 * with the stylesheet off (a "disable CSS" bug report, a text browser) and
 * photographed into a ticket. The three colours are WordPress' own admin palette
 * - `#46b450` (success), `#f0b849` (warning), `#dc3232` (error) - so an admin
 * colour scheme override applies to this table the way it applies to a core
 * notice, instead of fighting a private scale.
 *
 * `.bpe-diag--ok`, `.bpe-diag--warn` and `.bpe-diag--fail` are the contract the
 * live test and any probe read; the status word carries the meaning and these
 * only reinforce it.
 */

.bpe-diag {
        margin: 1em 0;
        max-width: 72em;
}

.bpe-diag th,
.bpe-diag td {
        text-align: left;
        vertical-align: top;
}

.bpe-diag .bpe-diag__label {
        width: 16em;
        font-weight: 600;
}

.bpe-diag .bpe-diag__status {
        width: 7em;
        font-weight: 600;
        white-space: nowrap;
}

.bpe-diag .bpe-diag__detail {
        color: #50575e;
}

.bpe-diag .bpe-diag__remedy {
        color: #1d2327;
}

.bpe-diag--ok .bpe-diag__status {
        color: #46b450;
}

.bpe-diag--warn .bpe-diag__status {
        color: #f0b849;
}

.bpe-diag--fail .bpe-diag__status {
        color: #dc3232;
}

.bpe-diag--fail .bpe-diag__detail {
        color: #dc3232;
}

/* The "Professional" badge of a locked settings row. */
.bpe-pro-badge {
        display: inline-block;
        margin-left: 0.4em;
        padding: 0 0.4em;
        border-radius: 3px;
        background: #2271b1;
        color: #fff;
        font-size: 11px;
        font-weight: 600;
        line-height: 1.7;
        letter-spacing: 0.02em;
        text-transform: uppercase;
        vertical-align: middle;
}

/* A locked row still shows what the setting does - only the control is inert. */
.bpe-pro-row--locked .description {
        color: #646970;
}

/*
 * The control of a locked row, dimmed but readable.
 *
 * The badge and the upgrade link said "locked" in words; the control itself
 * still looked exactly like the working "Enable Gutenberg Editor" checkbox,
 * because WordPress' admin styles overrule the grey a browser paints on a
 * `disabled` control. Opacity and the not-allowed cursor are the part that says
 * "this is not live" without hiding the state the row describes (a checked box
 * must still read as checked - it is what the licence would give).
 *
 * The label and the description are dimmed one step, not to the point of
 * illegibility: this half of the row sells the feature, so it has to be read.
 * Neither element gets `pointer-events: none` - the control is `disabled`, so a
 * click on the label already leads nowhere, and breaking the label would break
 * the row for anyone reading it with a screen reader.
 */
.bpe-pro-row--locked input,
.bpe-pro-row--locked textarea,
.bpe-pro-row--locked select {
        opacity: 0.5;
        filter: grayscale(1);
        cursor: not-allowed;
}

.bpe-pro-row--locked .checkbox {
        accent-color: #8c8f94;
}

.bpe-pro-row--locked label {
        color: #50575e;
        cursor: not-allowed;
}

.bpe-pro-cta {
        margin: 0;
        font-weight: 600;
}
