.dt-buttons .btn { margin-right: 5px !important; }
.unpaid_row{color:#fff !important; background-color:#FF4961 !important;}
.paid_row{color:#fff !important; background-color:#28D094 !important;}
.font_bold{font-weight:bold !important;}.error-msg{text-align:center; font-weight:bold;color:#FF0000;}
#list_error_div{padding-right:25px !important;}
.custom-td-fix{padding:5px !important;width:100px !important;}
.custom-td-variable{padding:5px !important;width:50px !important;}
.th_td_no_top_border{border-top:0px !important;}

/* ===========================================================================
   Support ticketing — conversation timeline (client + super-admin realms).
   Lives in common.css because that file is loaded unconditionally on every
   page in both realms, so the two views need no new asset gate.
   Logical properties (inline-start/end) throughout: this app renders RTL.
   =========================================================================== */
.sup-timeline { display: flex; flex-direction: column; gap: 14px; }

.sup-msg {
    border: 1px solid var(--aq-surface-border, #e5e9f0);
    border-radius: var(--aq-r-lg, 10px);
    padding: 12px 14px;
    background: #fff;
}
.sup-msg-head {
    display: flex; align-items: center; gap: 10px; flex-wrap: wrap;
    margin-bottom: 6px; font-size: 12px;
}
.sup-msg-who  { font-weight: 700; }
.sup-msg-name { color: #6b7280; }
.sup-msg-time { color: #9ca3af; margin-inline-start: auto; }
.sup-msg-body { white-space: normal; word-break: break-word; line-height: 1.7; }

/* The client's own messages, so a thread reads as a conversation. */
.sup-msg--us     { background: #f8fafc; border-inline-start: 3px solid var(--aq-brand, #1e9ff2); }
/* Support-team replies. */
.sup-msg--team   { border-inline-start: 3px solid var(--aq-success-700, #047857); }
/* Automated messages (the auto-close notice). */
.sup-msg--system { background: #fbfbfc; border-style: dashed; color: #4b5563; }

/* INTERNAL NOTES — super-admin realm only. This styling is a visual aid for
   the operator, NOT a security boundary: the client's timeline query never
   returns an internal row in the first place (Support_ticket_m). Never rely on
   a CSS class to hide privileged content. */
.sup-msg--internal {
    background: #fffbeb;
    border-inline-start: 3px solid var(--aq-warning-700, #b45309);
    border-color: #fde68a;
}
.sup-msg-ribbon {
    display: inline-block; font-size: 11px; font-weight: 700;
    padding: 1px 8px; border-radius: 999px;
    background: var(--aq-warning-50, #fef3c7); color: var(--aq-warning-700, #b45309);
}

.sup-msg-files { margin-top: 10px; display: flex; flex-wrap: wrap; gap: 8px; }
.sup-file {
    display: inline-flex; align-items: center; gap: 6px;
    font-size: 12px; padding: 4px 10px;
    border: 1px solid var(--aq-surface-border, #e5e9f0); border-radius: 999px;
    background: #fff; color: inherit; text-decoration: none;
}
.sup-file:hover { background: #f3f4f6; text-decoration: none; }

/* Sidebar unread badge, both realms. Populated by AJAX after paint, so it is
   hidden until it has a number to show. */
.aq-menu-badge {
    display: none;
    min-width: 18px; padding: 0 5px;
    margin-inline-start: 6px;
    border-radius: 999px;
    background: var(--aq-danger-700, #b91c1c); color: #fff;
    font-size: 11px; line-height: 18px; text-align: center;
}
.aq-menu-badge.is-on { display: inline-block; }