:focus
{
    outline: 0;
}
.ui-datagrid-header
{
    padding: 1px;
}
.ui-datagrid-header-noborder
{
    border-bottom: none!important;
}
.ui-datagrid-footer
{
    border: 0;
    height: 30px;
    left: 0;
    padding: 0;
    position: static;
    top: 0;
}

.activation_col {
    display: flex;
    justify-content: center;
    align-items: center;
}
.green-find-app{
    color:rgb(141, 194, 98);
}
.ui-datagrid-main-table td{border-right:none;}
.ui-datagrid-main-table td .center-realign {
    vertical-align: middle;
}
.ui-datagrid-main-table td .bottom-realign {
    vertical-align: sub;
}
.ui-datagrid-main-table td .top-realign {
    vertical-align: super;
}
.ui-datagrid-footer .ui-datagrid-button-bottom
{
    margin: 5px 3px 0 0;
}
.ui-datagrid-columns-content
{
    left: 0;
    position: absolute;
    right: 0;
    top: 0;
}
.ui-datagrid-columns-content table
{
    border-collapse: collapse;
}
.ui-datagrid-columns-content .ui-datagrid-main-table
{
    width: 100%;
}
.ui-datagrid-columns-content th
{
    cursor: pointer;
}
.ui-datagrid-main-table td,.ui-datagrid-main-table th
{
    overflow: hidden;
    padding: 0;
    -webkit-user-select: none;
}
.ui-datagrid-columns-content table
{
    table-layout: fixed;
}
.ui-datagrid-columns-content table tr {}
.ui-datagrid-columns-content table td {}
.ui-datagrid-slide,.ui-datagrid-save,.ui-datagrid-dynamic,.ui-datagrid-theme,.ui-datagrid-visualize,.ui-datagrid-print
{
    margin: 3px 0 2px 5px;
}
.ui-datagrid-slide,.ui-datagrid-button,.ui-datagrid-save,.ui-datagrid-dynamic,.ui-datagrid-button-bottom,.ui-datagrid-theme,.ui-datagrid-visualize,.ui-datagrid-print
{
    cursor: pointer;
    display: block;
    float: right;
}
.ui-datagrid-slide span,.ui-datagrid-button span,.ui-datagrid-save span,.ui-datagrid-dynamic span,.ui-datagrid-button-bottom span,.ui-datagrid-theme span,.ui-datagrid-visualize span,.ui-datagrid-print span
{
    margin: 0;
}
.ui-datagrid-button
{
    cursor: pointer;
    float: left;
    margin-right: 5px;
    margin-top: 0px;
}
.ui-datagrid-pag
{
    float: left;
    margin-right: 5px;
    margin-top: 3px;
}
.ui-datagrid-paginfo
{
    float: left;
}
.ui-datagrid-pag input
{
    font-size: .9em;
    width: 20px;
}
.ui-datagrid-pag {
    font-size: .9em;
    padding-right: 5px;
}
/* =========================================================================
 * Footer pager: rows-per-page is ONE control, not two
 * =========================================================================
 * jQuery UI's combobox draws a text input and a separate toggle <a>, and here they
 * were reading as two unrelated boxes with a clipped chevron between them:
 *
 *   - the input carried `padding: 0 2px 1px 2px !important` -- 1px more at the
 *     bottom than the top, which is the uneven padding the value sat inside;
 *   - the toggle was pinned to `width: 15px` while the glyph it holds is a 16px
 *     sprite tile, so the arrow was cut off on its right edge -- and jQuery UI
 *     centres an icon-only button's glyph with negative margins (measured
 *     -9px 0 -8px -8px), which pushed it further out of a box that small;
 *   - the wrapper carried `padding-right: 10px` and a 22px height next to 25px
 *     pager buttons, so the whole control sat low and short.
 *
 * The fix is the usual one for a segmented control: the WRAPPER owns the frame and
 * the children own nothing -- one border, one radius, one height, and a single
 * hairline as the seam. This is the DATAGRID-LEVEL copy: the same treatment
 * existed only under `.pf-owner-grid` in editor_uniform.css, which meant every
 * grid that had not opted into the owner-grid skin still drew the clipped version.
 *
 * LITERAL colours, no --pf-* token: this sheet is loaded by header_webgen.tpl and
 * therefore reaches published sites, where no token is defined and a var() would
 * resolve to nothing and take the whole declaration with it.
 */
.ui-datagrid-pag .ui-combobox {
    display: inline-flex;
    align-items: stretch;
    vertical-align: middle;
    /* The pager button height, so the control sits on their line rather than below it. */
    height: 25px;
    /* Explicit, because a shrink-to-fit wrapper resolved to 36px around halves that
     * need 36 + 22: they overlapped and the chevron was clipped to 7px wide. */
    width: 60px;
    padding: 0;
    border: 1px solid #d7dbe0;
    border-radius: 6px;
    background-color: #fff;
    /* Clips the children's own corners, so the frame is the wrapper's alone. */
    overflow: hidden;
}
/* Neither half may shrink: at their natural widths inside a flex line they would be
 * squeezed, which is what clipped the chevron in the first place. */
.ui-datagrid-pag .ui-combobox > * {
    flex: 0 0 auto;
}
.ui-datagrid-pag .ui-combobox .ui-combobox-input{
    /* Uniform on all four sides -- this is the padding the request is about. The
     * !important answers nothing but this rule's own history: the declaration it
     * replaces carried one, and jQuery UI's `.ui-widget input` sizing still applies
     * to this element. */
    padding: 0 4px!important;
    font-size: inherit!important;
    line-height: inherit!important;
    height: auto;
    width: 36px;
    margin: 0;
    border: 0;
    border-radius: 0;
    background-color: transparent;
    box-shadow: none;
    text-align: center;
}
.coupon_content .ui-datagrid-pag,.contact_content .ui-datagrid-pag,
.note_content .ui-datagrid-pag,.sms_content .ui-datagrid-pag,
.email_content .ui-datagrid-pag {
    margin-top: 0px!important;
}


.ui-datagrid-pag .ui-datagrid-current-page {
    height: 25px;
    box-sizing: border-box;
    font-size: inherit!important;
    line-height: inherit!important;
    /* Uniform, and matching the rows-per-page box beside it -- these two sit on the
     * same line and were drawing 19px vs 22px tall with different bottom padding. */
    padding: 0 4px;
    border: 1px solid #d7dbe0;
    border-radius: 6px;
    text-align: center;
}
/* The toggle half. 22px wide, not 15px: the glyph inside is a 16px sprite tile and
 * anything narrower crops it -- which is the "dropdown icon is not full visible".
 * Flex centring rather than jQuery UI's negative margins, which are undone below. */
.ui-datagrid-pag .ui-combobox a,
.ui-datagrid-pag .ui-combobox .ui-combobox-toggle {
    display: flex;
    align-items: center;
    justify-content: center;
    width: 22px;
    height: auto;
    margin: 0;
    padding: 0;
    border: 0;
    /* The only line inside the control: the seam between the two halves. */
    border-left: 1px solid #d7dbe0;
    border-radius: 0;
    background-color: transparent;
    background-image: none;
}
.ui-datagrid-pag .ui-combobox a:hover,
.ui-datagrid-pag .ui-combobox .ui-combobox-toggle:hover {
    background-color: #f6f7f9;
}
/* jQuery UI centres an icon-only button's glyph with negative margins and absolute
 * positioning; under flex centring those only push it back out of the box.
 *
 * `flex: 0 0 auto` is the load-bearing half. .button({text:false}) still emits a
 * `<span class="ui-button-text">` beside the glyph -- parked off-screen with
 * text-indent, but carrying `.4em` of padding, so it is ~11px WIDE. 16 + 11 inside a
 * 22px flex line means both children shrink, and the measured result was a 9px-wide
 * icon: the chevron cropped to just over half of itself. Hiding the empty span and
 * refusing to shrink the glyph is what actually makes it whole. */
.ui-datagrid-pag .ui-combobox .ui-icon {
    margin: 0;
    position: static;
    flex: 0 0 auto;
    width: 16px;
    height: 16px;
}
.ui-datagrid-pag .ui-combobox .ui-combobox-toggle .ui-button-text,
.ui-datagrid-pag .ui-combobox a .ui-button-text {
    display: none;
}
.ui-datagrid-hidden-draggable
{
    cursor: pointer;
    left: 0;
    padding: 0 5px;
    position: absolute;
    text-align: center;
    top: 0;
}
.ui-datagrid-hidden-draggable .ui-icon
{
    float: left;
}
.ui-datagrid-notvisible
{
    visibility: hidden;
    width: 0!important;
}
.ui-datagrid-loading img
{
    vertical-align: middle;
}
.ui-datagrid-loading table
{
    margin: 7px auto;
}
.ui-datagrid-loading td
{
    padding-right: 6px;
}
.ui-datagrid-loading
{
    display: none;
    left: 0;
    position: absolute;
    top: 0;
    z-index: 10;
}
.product-list-container .ui-datagrid-loading {left: 47%!important;top: 50%!important;}
.ui-datagrid-overflow
{
    overflow: auto;
}
.ui-datagrid-overflow-hidden
{
    overflow: hidden;
}
.ui-datagrid-overflow-hidden table
{
    position: relative;
}
.ui-datagrid-iefix
{
    border-right: none!important;
}
.ui-datagrid-oldiefix
{
    border-left: none!important;
}
.ui-datagrid-oldiefixbottom
{
    border-top: none!important;
}
.ui-datagrid-borderless-top
{
    border: none;
}
.ui-datagrid-borderless-bottom
{
    border-bottom: none!important;
}
.ui-datagrid-borderless-left
{
    border-left: none!important;
}
.ui-datagrid-borderless-right
{
    border-right: none!important;
}
.ui-datagrid-edit-placeholder td.ui-widget-content {
    border: none;
}

.ui-datagrid-edit-placeholder td select.minutes
{
    margin-left: 5px;
}
.ui-datagrid-edit-placeholder .inline_sel
{
    display: inline-block;
    margin: 0 5px 0 0;
}
.ui-datagrid-edit-placeholder input
{
    vertical-align: middle;
}
.ui-datagrid-edit-placeholder textarea,.ui-datagrid-edit-placeholder input
{
    width: 100%;
}
.ui-datagrid-edit-placeholder .hasDatepicker
{
    width: auto;
}
.ui-datagrid-edit-placeholder textarea
{
    height: 200px;
}
.ui-datagrid-edit-placeholder .dgr-editor-seltimedate
{
    display: inline-block;
    width: 100px;
}
.ui-datagrid-edit-placeholder .dgr-editor-seltimedate label
{
    margin: 0 5px;
}
.ui-datagrid-edit-placeholder .dgr-editor-seltimedate .ui-combobox
{
    margin: 5px 0;
}
.ui-datagrid-edit-placeholder .dgr-editor-seltimedate .hour,.ui-datagrid-edit-placeholder .dgr-editor-seltimedate .minutes
{
    margin: 0 0 0 5px;
}
.ui-datagrid-sortable-all,.ui-datagrid-sortable-selected
{
    float: left;
    list-style-type: none;
    margin: 0;
    margin-right: 10px;
    padding: 5px 0;
    width: 180px;
}
.ui-datagrid-sortable-all li,.ui-datagrid-sortable-selected li
{
    cursor: pointer;
    margin: 0 5px 5px 5px;
    padding: 5px;
    width: 140px;
}
.ui-datagrid-sortable-selected
{
    margin: 0;
}
.ui-datagrid-sortable-placeholder
{
    height: 18px;
}
.ui-datagrid-sortable span,.ui-datagrid-sortable div
{
    border: none!important;
}
.datagrid-dynamic-header
{
    cursor: default;
}
.ui-datagrid-overflow .ui-datagrid-main-table
{
    border-left: none;
    border-top: 0;
}
.ui-datagrid-main-table
{
    border-collapse: collapse;
}
.ui-datagrid-main-table input
{
    padding: 0;
}
.ui-datagrid-clear
{
    clear: both;
}
.ui-datagrid-collapse
{
    height: 600px;
    /* overflow: hidden; */
    position: relative;
    width: 100%;
}

.listings-dialog .ui-datagrid-collapse{
    position: relative;
    width: 100%;
}
.listings-dialog .ui-datagrid-table-holder{
    height: inherit !important;
}

.ui-datagrid-table-holder {height:inherit;}
.ui-datagrid-collapse .__wrappp a.j-next{
    display:none;
}
.ui-datagrid-lockedcolumns-content .ui-datagrid-overflow table
{
    position: absolute;
}
.ui-datagrid-lockedcolumns-content th
{
    cursor: pointer;
}
.ui-datagrid-dynamic-dialog select
{
    height: 200px;
    margin-top: 5px;
    width: 168px;
}
.ui-datagrid-dynamic-dialog a
{
    display: block;
    height: 18px;
    margin-bottom: 4px;
    padding-top: 2px;
    width: 20px;
}
.ui-datagrid-edit-placeholder table
{
    border-collapse: collapse;
    width: 100%;
}
.ui-datagrid-edit-placeholder
{
    padding: 2px;
}
.ui-datagrid-edit-placeholder .ui-datagrid-edit-header
{
    text-align: right;
    width: 20%;
}
.ui-datagrid-groupby-td span
{
    cursor: pointer;
    float: left;
}
.ui-datagrid-not-visible
{
    display: none;
}
.ui-datagrid-th-content
{
    display: block;
}
/* The column title. DataGrid.class.js:2109 writes it as an inline span with
 * white-space:nowrap and nothing to stop it: a 42px "Status" column on a phone drew
 * "Status" 12px past its own cell, past the header table, and past the screen --
 * header cells sit outside the grid's horizontal scroller, so nothing could ever
 * scroll to the rest of the word. Made a shrinkable box so it ellipsises instead. */
.ui-datagrid-th-content span:not(.ui-icon)
{
    display: inline-block;
    max-width: 100%;
    overflow: hidden;
    text-overflow: ellipsis;
    vertical-align: top;
}
/* The sort caret belongs at the RIGHT EDGE OF THE COLUMN, and the box it used to be
 * positioned against is not that box.
 *
 * DataGrid.class.js:2106 wraps the label in <div width="NN%"><div class="ui-datagrid-th-content"
 * style="width:100%">, where NN% comes from the column model. That percentage resolves against
 * a much larger box than the rendered <th>, so the inner div collapses to a fraction of the
 * cell -- measured on the Invoices grid: a 174px th whose content box is 45px, a 291px th whose
 * content box is 133px. With `position:relative` on .ui-datagrid-th-content, `right:0` anchored
 * the caret to THAT box, dropping it 86-146px short of the cell edge and, on a narrow column,
 * straight on top of the header text ("Invoice Date" with the caret over the D).
 *
 * Anchoring to the th instead makes `right` mean the column's right edge, whatever the inner
 * div does. Vertically centred rather than pinned to the top, because the th is now taller than
 * the 16px glyph on the owner grids. */
.ui-datagrid-main-table th,
.ui-datagrid-header th,
.ui-datagrid-header-table th
{
    position: relative;
}
/* ...but the th is not the caret's containing block, and cannot be made into one: the
 * resizable wrapper between them carries `position:relative` from jQuery UI's .resizable(),
 * which its own .ui-resizable-e handle needs. That wrapper is the box that collapses --
 * DataGrid.class.js:2105 puts the column model's width on BOTH the th (where "30%" is a
 * column-width hint the table resolves against the row) and this inner div (where the same
 * "30%" means 30% OF THE CELL). Measured: a 174px th wrapping a 45px div.
 *
 * min-width, not width: an explicit width would beat the px width jQuery UI writes inline
 * while a column is being dragged, and .resizable()'s stop handler reads ui.size.width off
 * this element to store the new column width. During a drag the th is resized with it
 * (alsoResize, :5236), so the clamp is inert exactly when it would otherwise interfere. */
.ui-datagrid-main-table th > div.ui-datagrid-resizable,
.ui-datagrid-header th > div.ui-datagrid-resizable
{
    min-width: 100%;
    box-sizing: border-box;
}
.ui-datagrid-th-content .ui-icon
{
    position: absolute;
    right: 4px;
    top: 50%;
    margin-top: -8px;
}
.ui-datagrid-resizable .ui-resizable-se
{
    display: none!important;
}
.ui-datagrid-resizable .ui-resizable-s
{
    display: none!important;
}
.ui-datagrid-quarter-td
{
    width: 25%;
}
.ui-datagrid-collapse input
{
    margin: 0 5px;
}
.ui-datagrid-main-table td
{
    word-break: break-word;
    border-right-color: #ddd;
    border-right-style: solid;
    border-right-width: 1px;
    border-bottom-style: solid;
    border-bottom-width: 1px;
    border-bottom-color: #ddd;
    text-align: left;
    padding: 5px;
}
.ui-datagrid-main-table td div
{
    font-size: 13px !important;
}

.ui-datagrid-main-table tr
{
    /*line-height: 1.9;*/
}
.ui-datagrid-main-table th {padding: 2px 5px;}

#ress-container .ui-datagrid-main-table td,
.wiki_dgr_container .ui-datagrid-main-table td
{
    word-break: break-word;
    border-right-color: #ddd;
    border-right-style: solid;
    border-right-width: 1px;
    border-bottom-style: solid;
    border-bottom-width: 1px;
    border-bottom-color: #ddd;
    text-align: left;
    padding: 5px;
    border: none;
}

#ress-container .ui-datagrid-main-table tr,
.wiki_dgr_container .ui-datagrid-main-table tr
{
    border-bottom-color: inherit;
    border-bottom-style: none;
    border-bottom-width: 0;
    border-top-color: inherit;
    border-top-style: none;
    border-top-width: 0;
    text-align: left;
    border: none !important;
}
.ui-datagrid-groupby-td
{
    border-bottom: none!important;
    border-top: none!important;
}
.ui-datagrid-groupby-td
{
    font-weight: bold;
}
.ui-datagrid-overflow
{
    position: relative;
}
.ui-datagrid-overflow .ui-state-hover
{
    font-weight: normal!important;
}
.ui-datagrid-filter-tr input,.ui-datagrid-filter-tr select
{
    margin: 0;
    width: 100%;
}
.ui-datagrid-filter-tr select
{
    height: auto!important;
}
.ui-datagrid-edit-nav .ui-state-default
{
    cursor: pointer;
    display: block;
    float: left;
    margin-right: 5px;
    margin-top: 5px;
}
.ui-datagrid-edit-nav .ui-state-default span
{
    margin: 0;
}
.ui-datagrid-addfilter-td
{
    padding-left: 7px;
}
.ui-datagrid-external
{
    border: 0;
}
.ui-treeview-icon
{
    cursor: pointer;
    float: left;
    margin-right: 2px;
    padding: 4px 0 1px 0;
}
.ui-treeview-space
{
    float: left;
    margin-right: 2px;
    width: 16px;
}
.ui-treeview-nodisplay
{
    display: none;
}
.ui-treeview-second-icon
{
    float: left;
    margin-right: 2px;
}
.ui-context-menu
{
    border-collapse: collapse;
    cursor: pointer;
    left: 0;
    position: absolute;
    top: 0;
    width: 100px;
}
.ui-tooltip
{
    display: none;
    left: -10;
    padding: 10px;
    position: absolute;
    top: -10;
    width: 500px;
    z-index: 500000;
}
.ui-tooltip .ui-special-icon
{
    left: -11px;
    position: absolute;
    top: 6px;
}
.ui-datagrid-footer
{
    height:50px;
    line-height: normal!important;
    overflow: hidden;
    font-size: 10px!important;
}

.advs_splitter_mobile .ui-datagrid-footer
{
    height:50px;
    line-height: normal!important;
    overflow: hidden;
    font-size: 10px!important;
}

.ui-datagrid-footer table {
    /* position:absolute;*/
}
.error_datagrid
{
    margin-bottom: 5px!important;
    margin-top: 0!important;
}
.ui-tabs-transform ul
{
    line-height: .5;
}
.ui-many-display
{
    width: 100%;
}
.ui-many-display th
{
    cursor: inherit;
    font-weight: normal;
    padding: 5px;
}
.ui-many-display input
{
    padding: 2px;
}
.subview-triggerer
{
    cursor: pointer;
    padding: 1px!important;
}
.datagrid-print-table
{
    border-collapse: collapse;
    margin: 5px 0;
}
.datagrid-print-table th,.datagrid-print-table td
{
    border: 1px solid;
    padding: 2px 5px;
}
.datagrid-print-table td *
{
    height: auto!important;
    width: auto!important;
}
.jportal_datagrid
{
    overflow: hidden;
    position: relative;
}
.portlet_only .__body .jportal_datagrid {margin-top: -2px;}
.ui-datagrid-group-dialog .ui-datagrid-group-button
{
    height: 16px;
    padding: 2px;
    width: 16px;
}
.ui-datagrid-group-dialog select
{
    margin-right: 5px;
    width: 215px;
}
.ui-datagrid-link-dialog
{
    height: 100%;
    width: 100%;
}
.adv-search-container td.ui-widget-header
{
    padding: 0 5px;
}
.adv-search-container td.ui-widget-content
{
    padding-top: 10px;
    border: none;
    font-family: Arial, sans-serif!important;
}
.adv-search-container td.ui-widget-content table
{
    min-width: 150px;
    width: 100%;
}
.adv-search-container td.ui-widget-content input[type="text"]{
    border: 1px solid #ccc;
    width: 100%;
    height: 25px;
    padding: 5px 0 5px 5px;
    border-radius: 3px;
}
/* The multi-select control (a column configured as a checklist) is a field in this
 * panel like any other, so it reads at the panel's size and ink: 13px, #0f172a --
 * the grid cell's, the same pair the text inputs and the chips take.
 *
 * It was 12px Arial #555 -- three properties, all three disagreeing with the fields
 * above and below it, and the family !important is what kept it on Arial inside an
 * editor panel otherwise on Inter. `inherit` follows the panel wherever it is drawn
 * rather than naming a face this sheet cannot know (it ships to published sites).
 *
 * The !importants are kept, not added: they are answering jQuery UI's own button
 * theme, and dropping them here would hand the control straight back to it. */
.adv-search-container .ui-multiselect {
    font-family: inherit !important;
    font-size: 13px !important;
    color: #0f172a !important;
    height: 28px;
    cursor: pointer;
    padding: 0px 12px;
}
/* Same again at a weight that beats css/jportal2.css:3672, which pins
 * `font-size: 14px !important; color: #777 !important` on exactly this control with
 * (0,3,0). Equal specificity, and this sheet is loaded AFTER that one
 * (header.tpl:88 vs _css_core.tpl:56), so order decides it. The menu is named with
 * the button because they are one control: a 14px popup list under a 13px box is
 * the same mismatch one level down. */
.search_product .adv-search-container .ui-multiselect,
.search_product .adv-search-container .ui-multiselect-menu,
.search_product.adv-search-container .ui-multiselect,
.search_product.adv-search-container .ui-multiselect-menu {
    font-size: 13px !important;
    color: #0f172a !important;
}
.adv-search-container td.ui-widget-content input.min-value
{
    padding: 5px 0 5px 5px;
    display: inline-block;
    float: left;
    max-width:80px;
}
.adv-search-container td.ui-widget-content input.max-value
{
    padding: 5px 0 5px 5px;
    display: inline-block;
}
/*.adv-search-container td.ui-widget-content input.max-value:focus,
.adv-search-container td.ui-widget-content input.min-value:focus{
    border: none !important;
}*/
.adv-search-container .adv-slider-row{
    display: inline-block;
    width: 100%;
}
.adv-search-container input[type="number"]{
    width: 50px;
    padding: 5px;
}
.adv-search-container td.ui-widget-content input.min-date,.adv-search-container td.ui-widget-content input.max-date,.adv-search-container td.ui-widget-content input.max-value
{
    max-width: 80px;
}
.adv-search-container .adv_category_box{
    width: 100%;
    display: inline-block;
    padding-left:5px;
    cursor: pointer;
}
.adv-search-container .sbc-elm{
    width: 100%;
    display: inline-block;
    padding: 5px 0px;
}
.adv-search-container .sbc-elm:hover, .adv-search-container .pnl-h:hover   {background: var(--pf-adv-hover, #f9f9f9);}
.adv-search-container .sbc-elm .chkb{
    float: left;
    cursor: pointer;
}
.adv-search-container .sbc-elm.mobile_subcategory{
    padding: 7px 10px;
    display: inline-block;
    width: 100%;
    border: 1px solid #ddd;
    border-radius: 4px;
    cursor: pointer;
    margin-bottom: 2px;
}
.adv-search-container .sbc-elm.mobile_subcategory .chkb{
    margin-left: 0px;
}
.adv-search-container .sbc-elm .adv_subcategory_label{
    float: left;
    margin-top: -1px;
    margin-left: 7px;
    max-width: 150px;
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}
.adv-search-container .pnl-h{
    padding: 5px 0px;
}

.adv_category_box.border_row {padding-left:0;}
.adv_category_box.border_row .pnl-h{
        border: 1px solid #e1e1e1;
        padding:8px;
            
}
.adv_category_box.border_row .pnl-h .advsearch-field-label{
        padding-left: 25px;
    position: relative;
    margin-left:0;
    float: none;
}

.adv-search-container .pnl-h.mobile_checkbox{
    padding: 7px 10px;
    display: inline-block;
    width: 100%;
    border: 1px solid #ddd;
    border-radius: 4px;
    cursor: pointer;
    margin-bottom: 2px;
}
.adv-search-container .pnl-h .category-inp{
    float: left;
    cursor: pointer;
}
.adv-search-container .pnl-h .advsearch-field-label{
    margin-top: -1px;
    margin-left: 25px;
    vertical-align: middle;
    font-size: 13px;
    line-height: 16px;
    /*float: left;*/
    color: #202124;
}
.adv-search-container .advsearch-field-label{
    font-size: 13px;
    line-height: 16px;
    font-weight: 600;
}
.adv-search-container .sbc-hidden-list {
    display: none;
    float: left;
    width: 100%;
    padding-left: 20px;
    margin-top: 10px;
}
.adv-search-container .fixed-advsearch{
    padding: 15px 0;
}

@media (min-width: 600px) {
    .scheduler_services{
        display: none;
        width: 250px;
        height: 80%;
        background-color: white;
        border-radius: 10px;
        position: absolute;
        top: 0;
        padding: 10px;
        left: 260px;
    }
}


.adv-search-container .control {
    position: relative;
    /* padding-left: 30px;
    margin-bottom: 15px;*/
    cursor: pointer;
    color: #202124;
}
.adv-search-container .control input {
    position: absolute;
    z-index: -1;
    opacity: 0;
}
.adv-search-container .control__indicator {
    position: absolute;
    top: 2px;
    left: 0;
    height: 20px;
    width: 20px;
    background: #e6e6e6;
    border-radius: 4px;
}
.adv-search-container.fixed-advsearch{    padding: 0 8px;}
.adv-search-container .sbc-hidden-list {    margin-top: 4px;}
.adv-search-container .control.sbc-elm .adv_subcategory_label{    margin-left: 25px;}


.adv-search-container .control:hover input ~ .control__indicator,
.adv-search-container .control input:focus ~ .control__indicator {
    background: #ccc;
}
.adv-search-container .control input:checked ~ .control__indicator {
    background: #2aa1c0;
}
.adv-search-container .control:hover input:not([disabled]):checked ~ .control__indicator,
.adv-search-container .control input:checked:focus ~ .control__indicator {
    background: #0e647d;
}
.adv-search-container .control input:disabled ~ .control__indicator {
    background: #e6e6e6;
    opacity: 0.6;
    pointer-events: none;
}
.adv-search-container .control__indicator:after {
    content: '';
    position: absolute;
    display: none;
}
.adv-search-container .control input:checked ~ .control__indicator:after {
    display: block;
}
.adv-search-container .control--checkbox .control__indicator:after {
    left: 8px;
    top: 4px;
    width: 3px;
    height: 8px;
    border: solid #fff;
    border-width: 0 2px 2px 0;
    transform: rotate(45deg);
}
.adv-search-container .control--checkbox input:disabled ~ .control__indicator:after {
    border-color: #7b7b7b;
}


.widget_searcher .ui-widget-content .search-box-0{
    display: block;
}

.widget_searcher .ui-widget-content .search-box-0 div{
    display: inline-block;
    margin-bottom:5px;
    margin-top: 5px;
}

.widget_searcher .ui-widget-content .search-box-0 div input{
    width: 70px;
}


.ui-datagrid-main-table a,.res-container a
{
    text-decoration: none;
}
.ui-datagrid-filter-dialog .ui-combobox {
    padding-right: 25px;

}
.ui-datagrid-filter-dialog input{
    border: 1px solid #ddd;
    padding: 0.2em;
}
.ui-datagrid-filter-dialog .ui-combobox-toggle  {margin-bottom:0px}
.ui-datagrid-filter-dialog .sel_filter_type .ui-combobox-input {width:80px; line-height: 23px;
                                                                padding: 0px!important;}
.ui-datagrid-filter-dialog .sel_filter_col .ui-combobox-input {width:100px;line-height: 23px;
                                                               padding: 0 0px!important;}
.ui-datagrid-filter-dialog .ui-icon{
    background-image:url(images/ui-icons_ffffff_256x240.png);
}
.adv-search-container {border:none;/*box-shadow: 1px 0px rgb(228, 227, 227);*/
                       -webkit-touch-callout: none; 
                       -webkit-user-select: none; 
                       -khtml-user-select: none; 
                       -moz-user-select: none; 
                       -ms-user-select: none; 
                       user-select: none;
}
.adv-search-container .buttonset label { min-width: 70px; }

/* =========================================================================
 * Add, at the top of the grid
 * =========================================================================
 * The toolbar twin of the footer's green + (DataGrid.class.js init_html). It shares
 * the footer copy's class, so it is wired and gated by the same code; only the look
 * is separate, because the footer rule is scoped to `.ui-datagrid-footer`.
 *
 * Slightly smaller than the 26px footer circle and without its drop shadow: it sits
 * in a row of 16px toolbar glyphs, and a shadowed 26px disc among them reads as a
 * floating action button that has landed in the wrong place.
 *
 * The glyph is the same data URI the footer + uses -- inline rather than a file
 * because this sheet is served to published sites, where a relative image path
 * resolves against a different directory.
 */
.ui-datagrid-header .ui-datagrid-add-top {
    float: right;
    width: 22px;
    height: 22px;
    margin: 3px 5px 2px 0;
    border-radius: 30px;
    cursor: pointer;
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAhklEQVQ4T92Tyw2AMAxD7QkYAdiEUcpkMAqjtBuwQVCkIuXQRFScoMd8XiM7IZwnIguAraZXkkerlAEgAxhrPpOcewFiG0g2P4sm+ArAqD15gjpxFXmliFi1OxnICjgBDL2dtb4oQBdmN54/ZRUA6Q82BrfwehOtO4Vkc08iEW93dMjknfMFHWhIRAbnWSIAAAAASUVORK5CYII=')!important;
    background-color: #569D28!important;
    background-position: 3px 3px;
    background-repeat: no-repeat;
    background-size: 16px 16px;
    border: 0;
}
.ui-datagrid-header .ui-datagrid-add-top:hover {
    background-color: #4a8722!important;
}
.ui-datagrid-footer .ui-datagrid-button-bottom {
    width: 26px;
    background-position: 5px 5px;
    height: 26px;
    border-radius: 30px;
    cursor: pointer;
    background-repeat: no-repeat;
    background-size: 16px 16px;
    cursor: pointer;
    box-shadow: 1.5px 2.6px 8px rgba(0, 0, 0, 0.27);
    margin-right: 5px;
    margin-top: 1px;
}
.ui-datagrid-footer .ui-datagrid-add {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAhklEQVQ4T92Tyw2AMAxD7QkYAdiEUcpkMAqjtBuwQVCkIuXQRFScoMd8XiM7IZwnIguAraZXkkerlAEgAxhrPpOcewFiG0g2P4sm+ArAqD15gjpxFXmliFi1OxnICjgBDL2dtb4oQBdmN54/ZRUA6Q82BrfwehOtO4Vkc08iEW93dMjknfMFHWhIRAbnWSIAAAAASUVORK5CYII=')!important;
    background-color: #569D28!important;
    background-position: 4px 4px;
}
.ui-datagrid-footer .ui-datagrid-button-bottom .ui-icon {
    display:none;
}
.ui-datagrid-footer .ui-datagrid-edit {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAABdUlEQVRIS7WVgVHDMAxF6w0YoZ0ARkg3gAloJ4Bu0A1oJiBMQDcgTECYgHQC0gnC/z65J1ybJo7xna4+pfe+JMuWmU1cfd9fAfEEu4V1sJ0xpnRYM4Uv8DcwbjxOBZE1fTkEanCuA4FakSQBifwV0A2shcVENqMFVFkWABeIshFfSKQZJRCB7yBURTI5DBaIwAm+l+5ZBkTKQQJet6xRlgo+B3fnW8L/qMpFf3FRYCD8BfAV/rsCtJFMZvB1fwokwJ8Bfwe4uHjREuGf0lm80XYFM8gFDwrkhJ8J5Ib/EvgPuC8wh4PXfRvpc92K7JazA3UHq3/tITN69qz7ELhESfBTBgByWHBo8LpzgHyoKJLhWoAP1gPsDsab+CUCk+BagFAOjRqlWiIjnscc+xp7TitOrQOMz/OplKGa+z4j3fOtPtiDhh3lrW+xJ3Q03GYg9ed08lcLgYVk042N3MEo4OrvfCwFs6DtU8FaYC8lsFAAWZJs6weY6SLYl+bLswAAAABJRU5ErkJggg==')!important;
    background-color: #569D28!important;
}
.ui-datagrid-footer .ui-datagrid-delete, .ui-datagrid-footer .ui-datagrid-del {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAUUlEQVQ4T2NkoBAwUqifYdQABgbG////OzAwMMxnYGBQIDFAHzAwMCSCDAAx5EnUDFP+AGTABwYGBn4yDXgI88ICMlzxkIGBIWE0HTAMgrwAAIe/FEQH4UIMAAAAAElFTkSuQmCC')!important;
    background-color: #dd0017!important;
}

.ui-datagrid-footer .ui-datagrid-filter{
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAABJElEQVQ4T5WT4TUEQRCEv8pACESACFwGTgTI4ETgROCJABEgAi4DIiAEIiiv1sy9mbtdnvozO93TNTXdtWICts+AU2BWjnwAj8CNpHwP0Ga97QPgFsg6hXNJd1sEtneAdyDrXxhIOgW2wxrZwRewqDcVZcnvl/wnsLcmsL1bbq83H0p6HXliYpXkoiWYAw+l4ElS9luw3Z+rJ2wvgcuyv5KU/RhBpvJcEqtWQcaW7gf3krL/F0Hbg58GSVk72I4XjtdK26ztF+CoxNKsk2qaMuJroFXWTSGzz9s2DRTSIPHWH3HkYuhBYR8rHmtD1yNNFMdEeWs1VSV6A5aSkhsQgtZ9iaV4Vk1ke/0ztT9RS9A2riue0t/GoyDOioqMbD5m39+IvgGiToFMXmidDQAAAABJRU5ErkJggg==')!important;
    background-color: #7E7D99!important;
    background-position: 4px 4px;
}
.ui-datagrid-footer .ui-datagrid-groupby {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAA/ElEQVQ4T5WT4VHCQBCFv9cBJUgF0oF0IB04VGCoQO0AOpAKtANjBdIBLWgFj9nMnZMcRwj7J5PJ7du3372IiWW7Ae6BnaRDbtOUfttL4Kt3di3pPd6vCtieAUcgnv3qRKYItMDDBafzUQHbr8DLyJr7gUBqcIAC7oCfK4zWpcAn8Aj8psZy76z3B6wktaVASbtm4Ds1d0POGNjeAs8XrG8kxff/qkK0XZIPy8t+gKpBSnce1N+A4JGvL+zOJWU2dQe2I11PKa5Nsc6Z/QGD3p3vgSZPSzGO/+AgKXIxqI6B7RXwEdZrh8ayINuLtG9Mjb1vqhAIe22N8BSlEwhrYSir0zluAAAAAElFTkSuQmCC')!important;
    background-color: #7E7D99!important;
}
.ui-datagrid-footer .ui-datagrid-adv-search{
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAABSElEQVQ4T5WS4TVDQRSEZypAB1SACkQFdEAqEB1QAamADkQFoYN0QDqICsb53tkbm5z4kf3z9u3OnXtnZq1uJRlJupN03Y5XkmaSHm1/99jam02SQ0lPkm53gdrZxPZ0+74IXiXdSPqR9EBXOiY5a6RMxRrbBrtebmPPW/HI9mK7SxIme5GEpBPbfIcFARqvJN3bfm6S6Dy3fVTAJDXlGlcEaSCYa+wLSZBh6rKdY+ybpHfbZfIwwUBgu/xgvINOxlDQSf20DfFaQhWcl/4CF2mTVT4QKUavCUrb1PakgY+R0I+a5EMS0jaSQALgr/9iaoTVBD/A/8XYAHTmIbEAkwzSADN6aSbiy40Yu5gA4nxvYF0vJVFM3DxpZCBJg/MdCU8aooqJokW9viT8n/ZyNwh6sl37JPUW6nq8F8FWnPyu9iboSPBr9gvB+5/3lW+OQAAAAABJRU5ErkJggg==')!important;
    background-color: #7E7D99!important;
}

.ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-edit {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAABQklEQVQ4T52TQU7CQBSG/zdjpUuO0JWy7A0sNygLiDtLgnuOwA2EPaYsjZqIJ6DeQHe4kiPgjtJ2npkmY1oUGJ31fF/e//I/guULY6/pKPeGgIgZSSY3nXl/tSZLHr3pWQgST+Y/M79mMm1bCbrT87GUNC4UAgLiiuT5qKA3bc00sJWboQPHg5K+kTDz50FBDS4aCxA8CNU2Emae7BXswkTkA/y2FWngwm3mObzH62Xyq+AQfFq4YwavHwbvQx3th+AYrKH7wTIyi6wJ/grXJvgP/C3QLTtRjSgX6cwpGovqwnTm3bGr5Ssj6KJkMh05yp0TcGG2fQwuJ7iMW55S+ACrDkj4DASZ2IQ2cCno3rYi3SzdbRYY5ZS+6DiCya9ue9/NULk8wlWl3xMdR1+azaHpCRJirJiQSIHkrr9c2YDmzxcqXcqoJEQxPwAAAABJRU5ErkJggg==')!important;
    background-color: transparent!important;
    background-position: 4px 4px;
    border-radius: 20px!important;
    background-repeat: no-repeat;
    background-size: 20px 20px;
    cursor: pointer;
    box-shadow: 1.5px 2.6px 8px rgba(0, 0, 0, 0.27);
    margin-right: 5px;
    margin-top: 1px;
    border-color: transparent!important;
    line-height: 18px;
    font-size: 12px;
    width: 2.4em;
    height: 2.4em;
}

.ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-delete {
    background-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAW0lEQVQ4T2NkoBAwUqifYdQABgbG5yIaDv+YGeczMDAqkBag/x8w/f2fyPhUXPMBAwOjPGmaYar/P2B8Iqb5gZGRkZ9MAx7CvLCAdFf8f8j093/CaDpgGAR5AQBFDxbg8oxwPQAAAABJRU5ErkJggg==')!important;
    background-color: transparent!important;
    background-position: 4px 4px;
    border-radius: 20px!important;
    background-repeat: no-repeat;
    background-size: 20px 20px;
    cursor: pointer;
    box-shadow: 1.5px 2.6px 8px rgba(0, 0, 0, 0.27);
    margin-right: 5px;
    margin-top: 1px;
    border-color: transparent!important;
    line-height: 18px;
    font-size: 12px;
    width: 2.4em;
    height: 2.4em;
}
.contact_content .ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-edit, .contact_content .ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-delete{
    background-position:4px 4px;
}
.ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-edit .ui-icon, .ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-delete  .ui-icon,
.ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-edit .ui-button-text, .ui-datagrid-borderless-top .ui-button.ui-state-default.ui-datagrid-delete  .ui-button-text{
    display: none;
}
.adv-search-container .advsearch-field-label {
    display: block;
    /*    display: inline-block;
        float: left;*/
    /* ONE label-to-control gap for every field.
     *
     * The dialog builds each field as its own table row and left the spacing to
     * whatever the control brought with it, so the gap under "Invoice/Quote",
     * "Invoice type", "Invoice date" and "Client name" were all different and the
     * column read as unaligned. 6px here, one row rhythm below.
     *
     * The slider row ("Total sum") used to opt out of this with an inline
     * `margin-bottom:0; margin-top:5px`, which read as a squashed label sitting on
     * top of its own From/To row while every other field breathed. That inline
     * override is gone, and the slider's inputs no longer carry a top margin, so
     * this 6px is now the ONE label-to-control gap in the panel. */
    margin: 0 0 6px 0;
}

/* A column built with display:false. The row still has to exist -- collectFilters
 * walks every tr and reads its control -- so it is hidden, not dropped. `.invisible`
 * itself lives in jportal.css, which the editor loads but a published site does not;
 * this sheet reaches both, so the rule is repeated here rather than assumed. */
.adv-search-container tr.invisible {
    display: none !important;
}

/* Same deal for the row/update editor: a column hidden with edit_display or
 * update_display keeps its control (saveData reads every one of them and sends
 * the row back whole), so only the rule below takes it off the screen. Owner
 * pages run this dialog on the PUBLISHED site, which does not load jportal.css,
 * so without this the "hidden" fields would simply still be there. */
.ui-datagrid-edit-placeholder tr.invisible {
    display: none !important;
}

/* The same row form in the owner-page side panel (datagrid.editor.js openForm,
 * PF.ui.panel with cls pf-dg-form). Owner pages draw it on the published site
 * too, where editor_uniform.css's `.ui-dialog [class*="dialog_edit_dt_"]` look
 * never reaches, so the flat form is spelled out here with literal colours.
 * The markup is the dialog's: one cell per field, the zebra painted INLINE on
 * the cells (hence !important), the inputs given an inline 20px height by the
 * editor. Previous / Next live in the panel's bar, so the in-form arrows go. */
.pf-dg-form .ui-datagrid-edit-nav {
    display: none;
}
.pf-dg-form .ui-datagrid-edit-placeholder {
    padding: 0;
}
.pf-dg-form .ui-datagrid-edit-placeholder td,
.pf-dg-form .ui-datagrid-edit-placeholder td.ui-widget-content {
    background: transparent !important;
    border: 0;
    padding: 0 0 14px !important;
    color: #0f172a;
}
.pf-dg-form .ui-datagrid-edit-placeholder td.ui-datagrid-edit-header {
    width: auto;
    text-align: left;
    padding-bottom: 4px !important;
}
.pf-dg-form .ui-datagrid-edit-placeholder label,
.pf-dg-form .ui-datagrid-edit-placeholder td > div:first-child {
    float: none !important;
    font-size: 13px;
    font-weight: 500;
    color: #475467;
}
.pf-dg-form .ui-datagrid-edit-placeholder td > div + div {
    padding: 4px 0 0 !important;
}
.pf-dg-form .ui-datagrid-edit-placeholder input[type="text"],
.pf-dg-form .ui-datagrid-edit-placeholder input[type="email"],
.pf-dg-form .ui-datagrid-edit-placeholder input[type="number"],
.pf-dg-form .ui-datagrid-edit-placeholder input[type="password"],
.pf-dg-form .ui-datagrid-edit-placeholder input:not([type]),
.pf-dg-form .ui-datagrid-edit-placeholder select,
.pf-dg-form .ui-datagrid-edit-placeholder textarea {
    box-sizing: border-box;
    max-width: 100%;
    height: 36px !important;
    padding: 0 10px;
    border: 1px solid #d7dbe0;
    border-radius: 6px;
    background: #fff;
    color: #0f172a;
    font-size: 14px;
    font-family: inherit;
    box-shadow: none;
}
.pf-dg-form .ui-datagrid-edit-placeholder textarea {
    height: 120px !important;
    padding: 8px 10px;
    resize: vertical;
}
.pf-dg-form .ui-datagrid-edit-placeholder input:focus,
.pf-dg-form .ui-datagrid-edit-placeholder select:focus,
.pf-dg-form .ui-datagrid-edit-placeholder textarea:focus {
    outline: 2px solid rgba(42, 107, 132, .35);
    outline-offset: 1px;
    border-color: #2a6b84;
}
.pf-dg-form .ui-datagrid-edit-placeholder input.ui-state-error,
.pf-dg-form .ui-datagrid-edit-placeholder select.ui-state-error,
.pf-dg-form .ui-datagrid-edit-placeholder textarea.ui-state-error {
    border-color: #d92d20;
    background: #fff6f5;
}
.pf-dg-form .error_datagrid {
    margin: 0 0 12px;
    padding: 8px 12px;
    border: 1px solid #fecdca;
    border-radius: 8px;
    background: #fef3f2;
    color: #b42318;
    font-size: 13px;
}

/* The `name_parts` editor: two boxes over one stored column. Side by side when
 * there is room and stacked when there is not, because this dialog is 700px on a
 * desktop and full width on a phone. Only the two boxes are laid out here -- the
 * carrier input beside them is display:none from the markup and must stay that
 * way, so nothing below selects on the bare input. */
.dgr-editor-nameparts {
    display: block;
    overflow: hidden;
}
.dgr-editor-nameparts > span {
    display: inline-block;
    vertical-align: top;
    width: 48%;
    min-width: 130px;
    margin: 0 2% 0 0;
}
.dgr-editor-nameparts > span > label {
    display: block;
    margin: 0 0 3px 0;
    font-size: 11px;
    color: #767676;
}
.dgr-editor-nameparts > span > input {
    display: block;
    width: 100%;
    box-sizing: border-box;
}
@media (max-width: 560px) {
    .dgr-editor-nameparts > span {
        display: block;
        width: 100%;
        margin: 0 0 8px 0;
    }
}

/* One vertical rhythm between fields. Spacing only, no colour: this sheet is
   loaded by header_webgen.tpl for PUBLISHED sites too, where the editor's --pf-*
   tokens do not exist.

   12px, down from 14. The Add-reservation form (reservationsOwnerPages.js) puts
   8px between its fields, but it is a three-column grid where a row break is
   visible on its own; this is one 250px column, where the only thing separating
   the last field from the next field's label is this number. 12 keeps the break
   obvious while staying four times the 3px a label sits above its own control --
   which is the ratio that makes a label read as belonging DOWNWARDS. */
.adv-search-container table > tbody > tr > td.ui-widget-content,
.adv-search-container table > tr > td.ui-widget-content {
    padding: 0 0 12px 0;
    border: 0;
    background: none;
}
/* Text inputs and dropdowns fill the field width, so the left edges of every
   control line up under their labels instead of stepping in and out. */
.adv-search-container td.ui-widget-content > .search-box-0 input[type="text"],
.adv-search-container td.ui-widget-content input.adv-search-text {
    width: 100%;
    box-sizing: border-box;
}
/* The chip groups are a control like any other: same 6px under the label from
   .advsearch-field-label, and NOTHING of their own before the next field -- the
   14px above is the panel's one row rhythm, and an extra 8px here is what made the
   gap under Status and Date Range visibly looser than the gap under Name, Email and
   Phone. */
.adv-search-container .pf-date-presets,
.adv-search-container .pf-optset {
    margin: 0;
}

/* =========================================================================
 * The search panel's Find button
 * =========================================================================
 * It is the panel's primary action, so it takes the primary button from
 * doc/EDITOR_STYLE_GUIDE.md section 3.3: accent ground #2a6b84 (--pf-accent), ink
 * #f1f9fc (--pf-on-accent, not pure white -- that rings against the button's own
 * edge), a #1f5265 (--pf-accent-dark) border that is also the hover ground, 28px
 * (--pf-control-h), 13px/600, radius 8px.
 *
 * The values are written out rather than named through the tokens ON PURPOSE:
 * rule 3 of that guide. This sheet is loaded by header_webgen.tpl, so it reaches
 * published sites, where no --pf-* token exists and every var() here would resolve
 * to nothing and silently kill the declaration it sits in.
 *
 * Three things about the markup drive the rest of it. jQuery UI's .button() wraps
 * the label in `<span class="ui-button-text">` with its own `.4em 1em` padding, so
 * the horizontal padding has to be set on THAT span, not on the button -- the
 * button's own padding would be added to it. The magnifier is a sprite tile whose
 * default image is dark grey (#454545) and therefore all but invisible on an accent
 * ground, so it is repointed at the white sheet. And `ui-state-default` paints a
 * gradient through background-image, which a background-color alone does not
 * remove.
 */
.adv-search-container .adv_find,
.jportal_datagrid .adv-search-container .adv_find,
.ui-dialog .adv-search-container .adv_find {
    height: 28px;
    padding: 0;
    margin: 5px 0 5px 5px;
    border: 1px solid #1f5265;
    border-radius: 8px;
    background-color: #2a6b84;
    background-image: none;
    color: #f1f9fc;
    cursor: pointer;
}
.adv-search-container .adv_find:hover,
.adv-search-container .adv_find.ui-state-hover,
.adv-search-container .adv_find:focus {
    background-color: #1f5265;
    background-image: none;
    border-color: #1f5265;
}
.adv-search-container .adv_find .ui-button-text {
    /* The icon and the word are two children on one line; the gap between them is
     * this row's, not a margin on the glyph. */
    display: flex;
    align-items: center;
    justify-content: center;
    /* THE left/right padding. jQuery UI's own is `.4em 1em` on this span, which at
     * the inherited size came out uneven against a button that also had padding. */
    padding: 0 14px;
    color: #f1f9fc;
    font-size: 13px;
    font-weight: 600;
    line-height: 26px;
}
.adv-search-container .adv_find .ui-button-text .ui-icon {
    /* !important answers the theme sheets, which set the sprite per icon class --
     * css/blue-theme.css and the jQuery UI theme both name a dark sheet for
     * .ui-icon-search and neither can be out-specified from here without one. */
    background-image: url(images/ui-icons_ffffff_256x240.png)!important;
    /* jQuery UI centres an icon-only glyph with negative margins and absolute
     * positioning; inside this flex row those only push it out of the button. */
    margin: 0 6px 0 0;
    position: static;
    flex: 0 0 auto;
}

.custom-datagrid-upload .__row .__col img {
    max-width: 100%!important;
    max-height: 100%!important;
    width: auto;
    height: auto;
    margin: 0px auto;
    display: block!important;
}
.custom-datagrid-upload .__wrap_row .row .col img{
    max-width: 100%!important;
    max-height: 100%!important;
    width: auto ;
    display: inline-block;
    position: relative;
    /*margin: 0 auto;*/
    vertical-align: middle;
}
.custom-datagrid-upload ._dg_tile .__row .__col{
    overflow: hidden!important;
}
.custom-datagrid-upload ._dg_tile:hover {
    /* background-color: red; */
}
.custom-datagrid-upload ._dg_tile .__row .__col.hov{
    position: absolute;
    top: 0;
    left: 0;
    display: table;
    width: 100%!important;
    background: rgba(241, 242, 243, 0.92);
    max-height: 100%!important;
}
.custom-datagrid-upload ._dg_tile .__row .__col .cont{ overflow: hidden;   height: 100%;text-align: center;}
.custom-datagrid-upload ._dg_tile .__row .__col.hov .cont{
    display: table-cell;
    overflow:auto;
    vertical-align: middle;
    text-align: center;
    height: 100%;
    position: absolute;
    width:100%;
}

.custom-datagrid-upload ._dg_tile .__row .__col.hov img.imghov {
    max-height: 50%!important;
}
.custom-datagrid-upload ._dg_tile .defaulttile.hov{
    position:absolute;
    overflow:auto;
}
.custom-datagrid-upload .controls .list_view, .custom-datagrid-upload .controls .grid_view {
    background-position: 1px 3px;
}
.custom-datagrid-upload .ui-datagrid-columns-content tr td img {
    max-width: 100%;
    max-height: 100%;
    width: auto;
    height: auto;
    display: inline-block;
    height: 80px;
    /*margin:0 auto;*/
}

.advs .ui-datagrid-pag-td {
    display: flex;
    align-items: center;
    justify-content: space-evenly;
    flex-wrap: wrap;
    padding-left: 4px;
}

@media (max-width: 600px){.widget_searcher .advs .ui-datagrid-pag-td {
    display: block;
    padding-left: 50px;
}
}

.advs .ui-datagrid-pag-td span { /*:nth-child(3)*/
    z-index: 10001;
    display: flex;
    align-items: center;
    justify-content: center;
    text-align: center;
}

.advs .ui-datagrid-paginfo {
    margin-top: 5px;
    width: 100%;
    text-align: center;
}

.advs .ui-datagrid-pag-td span:nth-child(6) {
    display: none;
}


#ui-datepicker-div .shed_duration {
    width: 120px;
    text-align: center;
}



.ui-slider-handle {
    border-radius: 50%!important;
}

.ui-datepicker-buttonpane button {
    border-radius: 4px!important;
}
._dg_tile.unavailable{
    display:none!important;
}
._dg_tile {
    transition: .35s all;
    display:inline-table!important;
    /* THE TILE IS A TABLE BOX, SO IT INHERITS border-collapse -- AND IN THE EDITOR IT INHERITED
       `collapse`, WHICH STOPPED ITS OWN BORDER FROM BEING PAINTED AT ALL.

       `border-collapse` is an INHERITED property, and website-generator.css:1861
       `.website_generator ._p_row` sets it to `collapse`. `._p_row` is the page editor's row
       wrapper -- a published page uses `.row`/`.col` and never has one -- so the declaration
       reached every tile on the admin canvas and no tile on the live site. In the collapsed
       model a table's own border is resolved against its cells' borders, and these tiles have
       only anonymous cells with no borders, so nothing was drawn.

       That is why this was so hard to read from the markup: the tile still carried
       `border-width:1px;border-style:solid;border-color:...` inline from the template
       (datagrid_block_render.js tileBoxCss), and getComputedStyle still answered `1px solid`,
       because computed style reports the specified value and not the used collapsed one. The
       block editor drew the border, the published site drew the border, the admin canvas did
       not, and all three agreed on every value you could inspect.

       Fixed here rather than in website-generator.css: that `border-collapse` is already dead
       weight there (the rule declares `display:table` and then `display:flex` two lines later,
       so the row is not a table box), but it is inherited by every descendant of every editor
       row, and removing it would change any other table-display element that has come to rely
       on it. Naming the value on the tile itself fixes the one box that is a table and leaves
       the rest of the canvas exactly as it was. Published sites already computed `separate`,
       so this changes nothing there -- it only stops the editor from differing. */
    border-collapse: separate;
    /* ...and having asked for `separate`, pay none of its spacing.
     *
     * `border-spacing` is ALSO inherited, and DataGrid.class.js:3388 wraps the tiles in a real
     * <table>, which picks up the UA stylesheet's `table { border-spacing: 2px }` and hands it
     * down. `._dg_tile` is `display:inline-table`, so it SPENDS that -- 2px at each edge, +4px
     * on the occupied width of every tile.
     *
     * It was inert while the tile inherited `collapse` (spacing is ignored under collapse). The
     * `separate` above is what woke it: the block suite measured a 340px tile occupying 346
     * (+2 border, +4 spacing) at two different widths -- a constant delta, which is what ruled
     * out a content-driven table minimum. DataGrid.class.js:3397 sizes tiles with jQuery
     * `.width()`, whose setter sets the CONTENT box, so the renderer's contract is
     * "content == the Width field" and the extra 4px was pure inherited noise.
     *
     * The tile has no cells of its own to space. Pinned by blk.set.width/rendered, which
     * decomposes the box by name and fails on any pixel that is not border, padding or spacing. */
    border-spacing: 0;
    /* The tile is sized in JS to the template's declared pixel width, and DataGrid.class.js now
       clamps that to the space available. This is the same guarantee expressed in CSS, so a tile
       can never be wider than the column it sits in even on a path that sets the width some other
       way - it is overflow:hidden below, and anything past the edge is silently cropped rather
       than wrapped. The rightmost columns of a wide card are its price and call to action. */
    max-width:100%;
    color:#777;
    height:220px;
    margin:10px 10px 10px 9px;
    width:230px;
    overflow:hidden;
    border:1px solid;
    border-color:#f3efef;
    position:relative;
    border-radius:0 0 5px 5px;
    cursor:pointer;
    background-color: transparent;
    /*margin:auto;*/
    /*transform: none!important;*/

}
/*@media (max-width: 1050px) {*/
    ._dg_tile {
        margin-left:auto;
        margin-right:auto;
        transform: none!important;
    }
/*}*/

._dg_tile:hover {
    -webkit-box-shadow: 0px 0px 9px 1px rgba(0,0,0,0.25)!important;
    -moz-box-shadow: 0px 0px 9px 1px rgba(0,0,0,0.25)!important;
    box-shadow: 0px 0px 9px 1px rgba(0,0,0,0.25)!important;
    -ms-transform: scale(1.02);
    -webkit-transform: scale(1.02);
    transform: scale(1.02);
}

#ui-datepicker-div {
    z-index: 99999999!important;
}

.det_h {
    margin-top: 5px;
    font-size: .9rem;
    line-height: 1.5rem;
}

.det_s {
    font-weight: 600;
    color: #5ba525;
}



.widget_searcher .ui-datagrid-main-table td {
    line-height: 1.5;
}

.invoice_manager .ui-datagrid-pag-td .ui-datagrid-pag{
    position: relative;
}
.invoice_manager .ui-datagrid-pag-td .ui-datagrid-paginfo{
    margin-top: 5px;
    width: 100%;
    color: #777;
    position: relative;
    margin-right: -60px;
    float: right;
}
.ui-datagrid-pag-td .ui-datagrid-first-page,.ui-datagrid-pag-td .ui-datagrid-previous-page,.ui-datagrid-pag-td .ui-datagrid-next-page,.ui-datagrid-pag-td .ui-datagrid-last-page{
    border-radius: 13px;
    height: 25px;
    width: 25px;
}
.ui-datagrid-button span{
    margin : 2px;
}
/* =========================================================================
 * Advanced search — quick date-range presets
 * =========================================================================
 * The chip row rendered by datagrid.advanced.search.js::pfDatePresetMarkup.
 *
 * IN THIS SHEET, and with LITERAL colours: the search dialog is drawn by the
 * DataGrid engine, which runs on published sites as well as in the editor, and
 * no --pf-* token is defined there (a var() would resolve to nothing and the
 * rule would silently die).
 *
 * ALL of the styling is here and none of it is inline on the markup. Inline
 * declarations beat stylesheet rules without !important, and a `background` set
 * inline is what stopped the selected chip from being colourable at all.
 */
.pf-segrid {
    /* A ROW OF PILLS -- the Add-reservation dialog's start-time list
     * (`.pfv-slot` in js/widgets/reservationsOwnerPages.js), which is the newest
     * form in the product and the one this panel is measured against.
     *
     * It was one segmented control on a fixed number of 1fr grid tracks: collapsed
     * borders, only the group's four outer corners rounded, and a builder that had
     * to compute which chip rounded which corner. Equal tracks force every chip to
     * the width of the longest -- "1 day" and "3 months" in the same box -- and a
     * ragged last row needed a spanning chip to hide the hole. A wrapping row of
     * pills has neither problem: each chip is as wide as its own word, the row
     * breaks where the panel ends, and no rule anywhere counts the items.
     *
     * 6px gap, and no bottom margin: the field's own <td> carries the panel's row
     * rhythm, so anything here would make the gap under Status and Date Range wider
     * than the gap under Name, Email and Phone. */
    display: flex;
    flex-wrap: wrap;
    gap: 6px;
    margin: 0;
    -webkit-user-select: none;
    user-select: none;
}

.pf-date-preset,
.pf-opt {
    /* ONE PILL, and every value in it is the reservation slot's: 5px/9px padding, a
     * #d3d8e0 edge, an 8px radius, white, and the panel's own 13px/1.45 type. The
     * ink is #0f172a -- the grid cell's, and the same the field boxes above take --
     * so a chip, a typed value and a row all read at one weight.
     *
     * Written as literals rather than named through the --pf-* tokens: this sheet is
     * loaded by header_webgen.tpl and therefore reaches PUBLISHED sites, where no
     * token is defined and every var() here would resolve to nothing and silently
     * kill the declaration it sits in.
     *
     * font-family: inherit, and that is the whole point of stating it. A <button>
     * does NOT inherit the family -- it takes the UA's own, which is how these chips
     * ended up in the browser's default face while every label and input around them
     * was on something else. `inherit` follows the panel: the editor's Inter in the
     * editor (css/editor_uniform.css names it on `.pf-owner-search`), the site's own
     * face on a published site.
     *
     * margin: 0 !important is load-bearing: jportal_base_mod_style.css sets
     * `button:not(.prev .next):not(.html-button) { margin: 2px 5px 2px 0 }`, whose
     * two :not() arguments give it (0,3,1) -- more than this class can reach without
     * stacking selectors. Without the override the flex gap is 6px on one side and
     * 11px on the other.
     *
     * A label is never wrapped mid-chip: `white-space: nowrap` is what makes the ROW
     * wrap instead, which is the whole layout. */
    min-width: 0;
    padding: 5px 9px;
    border: 1px solid #d3d8e0;
    border-radius: 8px;
    background: #fff;
    color: #0f172a;
    font-family: inherit;
    font-size: 13px;
    font-weight: 400;
    line-height: 1.45;
    text-align: center;
    cursor: pointer;
    white-space: nowrap;
    margin: 0 !important;
    /* Stops the ~300ms double-tap-zoom delay on touch. */
    touch-action: manipulation;
    transition: background-color .12s ease, border-color .12s ease;
}
/* THE PILL'S INK, stated a second time at a weight that can hold it.
 *
 * The rule above says #0f172a and the screen said #777: blue-theme.css:1 opens with
 * `.ui-widget input, .ui-widget textarea, .ui-widget keygen, .ui-widget select,
 * .ui-widget button { color: #777 }`, which is (0,1,1) -- more than a lone class --
 * and every one of these chips is a <button> inside the search dialog, which is a
 * .ui-widget. So the whole group rendered a shade paler than the labels above it and
 * the grid behind it, and nothing in this sheet said so.
 *
 * Two classes rather than an !important: `.pf-segrid` is the group these chips are
 * always in (pfDatePresetMarkup / pfOptsetMarkup both emit it on the wrapper), so
 * (0,2,0) is enough to win and leaves the selected/hover rules below free to change
 * the colour without an arms race. */
.pf-segrid .pf-date-preset,
.pf-segrid .pf-opt {
    color: #0f172a;
}
.pf-date-preset:hover,
.pf-opt:hover {
    background: #f6f7f9;
    border-color: #c3c9d1;
}
/* THE UNSELECTED SEGMENT'S INK, stated a second time at a weight that can hold it.
 *
 * The base .pf-date-preset rule says #0f172a and the screen said #777: blue-theme.css:1
 * opens with
 * `.ui-widget input, .ui-widget textarea, .ui-widget keygen, .ui-widget select,
 * .ui-widget button { color: #777 }`, which is (0,1,1) -- more than a lone class --
 * and every one of these chips is a <button> inside the search dialog, which is a
 * .ui-widget. So the whole group rendered a shade paler than the labels above it and
 * the grid behind it, and nothing in this sheet said so.
 *
 * Two classes rather than an !important: `.pf-segrid` is the group these chips are
 * always in (pfDatePresetMarkup / pfOptsetMarkup both emit it on the wrapper), so
 * (0,2,0) is enough to win and leaves the selected/hover rules below free to change
 * the colour without an arms race. */
.pf-segrid .pf-date-preset,
.pf-segrid .pf-opt {
    color: #0f172a;
}
.pf-date-preset:focus-visible,
.pf-opt:focus-visible {
    /* Outside the pill now that the pills no longer overlap each other. */
    outline: 2px solid #93c3d9;
    outline-offset: 1px;
}
/* Chosen. A filled pill rather than a border change: on a tablet, in daylight, a 1px
 * border shift is not a state you can see.
 *
 * The Find button's fill (2026-09-13, owner's call): accent ground #2a6b84, #1f5265
 * edge and hover, #f1f9fc ink -- the .adv_find values below, as literals because this
 * sheet reaches published sites. It was near-black (#0f172a, the Add-reservation
 * slot) so that Find stayed the only accent surface; the owner wants a chosen filter
 * to read as the same colour as the button that applies it. */
.pf-date-preset.pf-date-preset-on,
.pf-opt.pf-opt-on {
    background: #2a6b84;
    border-color: #1f5265;
    color: #f1f9fc;
}
.pf-date-preset.pf-date-preset-on:hover,
.pf-opt.pf-opt-on:hover {
    background: #1f5265;
    border-color: #1f5265;
}
/* Touch, detected as touch. This was `@media (max-width: 900px)`, which asks the
 * VIEWPORT -- useless here, because the search panel is ~250px wide whatever the
 * viewport is, so on a 1600px tablet the rule never applied. `pointer: coarse` asks
 * the actual input device. Height only: a min-width would overflow the fixed track
 * row instead of widening it. */
@media (pointer: coarse) {
    .pf-date-preset,
    .pf-opt {
        padding: 8px 11px;
    }
}
/* =========================================================================
 * Row status: a button and a menu, not a <select>
 * =========================================================================
 * Drawn by searchBookingOwnerPages.js (pfBookStatusButton). In THIS sheet and with
 * LITERAL colours for the same reason as everything above it: the owner screens run
 * on published sites as well as in the editor, and no --pf-* token is defined there.
 *
 * The values are the style guide's all the same -- #d7dbe0 control edge, #344054 ink,
 * #f6f7f9 hover, 8px radius, 13px type -- written out rather than named.
 *
 * Colour lives on the GLYPH, not on the button's ground. A row of filled badges in a
 * table column is a column of colour with the data as an afterthought, and five
 * grounds means five different contrast problems for one label; one coloured glyph
 * beside black-on-white text carries the state at a glance and stays legible.
 */
/* The cell wrapper. It used to carry `align="center"` plus inline top/bottom margins
 * of 10px each, which is where most of the booking row's height came from -- 20px of
 * margin around a 22px control, on every row. */
.search_item_status {
    display: block;
    margin: 4px 0;
    text-align: center;
}
.pf-status {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    max-width: 100%;
    height: 24px;
    padding: 0 8px;
    border: 1px solid #d7dbe0;
    border-radius: 8px;
    background-color: #fff;
    color: #344054;
    font-size: 12px;
    line-height: 22px;
    white-space: nowrap;
    cursor: pointer;
    /* Stops the ~300ms double-tap-zoom delay on touch. */
    touch-action: manipulation;
}
.pf-status:hover {
    background-color: #f6f7f9;
    border-color: #98a2b3;
}
/* Paid is terminal. Muted rather than greyed to illegibility -- it is still the row's
 * state and has to be readable, it just cannot be changed. */
.pf-status[disabled],
.pf-status.pf-status-locked {
    cursor: default;
    opacity: .7;
    background-color: #fff;
    border-color: #e6e8ec;
}
.pf-status .fa {
    font-size: 12px;
    flex: 0 0 auto;
}
.pf-status .pf-status-label {
    /* A flex item's min-width is its content, so without this the label never
     * shrinks: it spilled 3-6px past the button (and the phone) on the List tab
     * instead of ellipsising, once the table stopped being window-wide. */
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
}
/* The one place a status carries colour. */
.pf-status-pending    .fa { color: #b54708; }
.pf-status-approved   .fa { color: #2a6b84; }
.pf-status-unapproved .fa { color: #b42318; }
.pf-status-invoice    .fa { color: #667085; }
.pf-status-paid       .fa { color: #067647; }

/* The menu. Appended to <body> -- the grid body clips and scrolls its own content, so
 * a menu drawn inside a cell is cut off on the last visible row. */
.pf-status-menu {
    position: absolute;
    /* Above the datagrid's own chrome and the splitter, below a jQuery-UI dialog
     * (which sits at 1000+ and would otherwise be covered by a menu opened behind it). */
    z-index: 999;
    display: flex;
    flex-direction: column;
    min-width: 132px;
    padding: 4px;
    border: 1px solid #d7dbe0;
    border-radius: 8px;
    background-color: #fff;
    box-shadow: 0 16px 32px -12px rgba(16, 24, 40, .22);
}
.pf-status-menu .pf-status-opt {
    display: flex;
    align-items: center;
    gap: 8px;
    width: 100%;
    height: 28px;
    padding: 0 8px;
    border: 0;
    border-radius: 6px;
    background-color: transparent;
    color: #344054;
    font-size: 13px;
    text-align: left;
    white-space: nowrap;
    cursor: pointer;
}
.pf-status-menu .pf-status-opt:hover {
    background-color: #f6f7f9;
}
.pf-status-menu .pf-status-opt .fa {
    width: 14px;
    flex: 0 0 auto;
}

/* The From/To fields sit under the chips and were clipping their own value
 * ("27 Aug 202" / "03 Sep 202") in the narrow search panel.
 *
 * The [pname=start_date]/[pname=end_date] pair belonged to the Orders screen's
 * own hand-built search dialog, which is gone — Orders mounts the datagrid's
 * advanced search like every other owner screen — but the selector is kept
 * because it is the markup .adv_search emits generally, not something only that
 * dialog produced. */
.adv-search-container .min-date,
.adv-search-container .max-date,
.adv_search .adv-range-item input[pname="start_date"],
.adv_search .adv-range-item input[pname="end_date"] {
    min-width: 96px;
    box-sizing: border-box;
}

/* =========================================================================
 * Orders — the grid cells and the order dialog
 * =========================================================================
 * WHY HERE AND NOT IN editor_uniform.css
 * That sheet is loaded by header.tpl / headertemplates.tpl / mobileheader.tpl
 * only — NOT by header_webgen.tpl, which is what renders an owner page in the
 * preview and published contexts. A rule for an owner screen that lives there
 * is invisible on half the surfaces the screen appears on; that is what left
 * the rows-per-page chevron clipped after it had "already been fixed".
 *
 * So: literal colours, no var(--pf-*) — the token block is declared in the
 * editor-only sheet and is undefined here (doc/EDITOR_STYLE_GUIDE.md rule 3).
 * The values below are the ones those tokens resolve to.
 *
 * Every selector is scoped to .orders_customers (the Orders widget root) or to
 * .pf-order-dialog (its detail dialog), neither of which a published page has.
 */

/* The strip the Search icon sits in.
 *
 * js/widgets/modules/owner_toolbar.js positions its icons absolutely inside the
 * widget root, so the wrapper it names has to reserve room or they land ON the
 * column header row. editor_uniform.css declares the same 44px against each
 * owner wrapper BY NAME — it has to, so the padding is in effect at first paint,
 * before owner_grid_fit measures — but that sheet never reaches the preview and
 * published surfaces, where the same screens render through header_webgen.tpl.
 * This is the class the module itself applies, so the strip exists on both.
 *
 * Structural, not a token: 44px is the clear space Invoices has always had. */
.pf-owner-toolbar-band {
    padding-top: 44px;
    box-sizing: border-box;
}

/* The order number is the only thing on the row you can click, so it has to
 * look like it: a link, not a button, because it opens a view rather than
 * changing anything. It is a <button> in the markup for the keyboard and for
 * the screen reader — the appearance is reset here rather than losing that. */
.orders_customers .pf-order-no {
    padding: 0;
    border: 0;
    background: none;
    font: inherit;
    font-weight: 600;
    color: #1a6ed8;
    cursor: pointer;
    text-align: left;
    white-space: nowrap;
}
.orders_customers .pf-order-no:hover,
.orders_customers .pf-order-no:focus {
    text-decoration: underline;
    outline: 0;
}
.orders_customers .pf-order-no:focus-visible {
    outline: 2px solid #1a6ed8;
    outline-offset: 2px;
}
/* On the selected row the grid paints its own ground, and a blue link on it is
 * the one thing that stops being readable. */
.orders_customers .ui-state-highlight .pf-order-no {
    color: inherit;
}
/* The order whose detail panel is open. The panel is NOT modal — the grid stays
 * live behind it so the next number can be clicked straight into it — which
 * makes "which of these am I looking at?" a real question the moment the panel
 * is dragged aside. */
.orders_customers .pf-order-no-open {
    text-decoration: underline;
    text-underline-offset: 3px;
}
.orders_customers .pf-order-no-open::before {
    content: "";
    display: inline-block;
    width: 6px;
    height: 6px;
    margin-right: 5px;
    border-radius: 50%;
    background-color: #1a6ed8;
    vertical-align: 1px;
}

/* The ROW whose detail panel is open, on Invoices and on Clients.
 *
 * Both panels became non-modal and reusable so that clicking the next row swaps
 * the contents in place — the behaviour the Orders screen already had. That is
 * only usable if the grid says which row is on screen: the panel can be dragged
 * anywhere, and on Clients it carries no id of its own at all.
 *
 * A left bar rather than a background: these grids already use the background to
 * mean hover and selection, and a third meaning competing for the same channel
 * reads as a rendering fault. `box-shadow: inset` rather than `border-left` so
 * nothing reflows by 3px when the mark appears.
 */
tr.pf-invoice-no-open > td,
tr.pf-contact-row-open > td {
    background-color: #eef4fd;
}
tr.pf-invoice-no-open > td:first-child,
tr.pf-contact-row-open > td:first-child {
    box-shadow: inset 3px 0 0 0 #1a6ed8;
}

/* --- Invoices: the invoice number, same treatment ------------------------
 * The invoice number opens the invoice, so it has to look like a way in rather
 * than like data. It is a <button> in the markup for the keyboard and the
 * screen reader; the appearance is reset here rather than losing that.
 *
 * Deliberately the same rules as .pf-order-no above -- the two owner screens
 * are read side by side and the one clickable cell on each should not be a
 * different colour. It lives in THIS sheet, not editor_uniform.css, because
 * that one does not reach an owner page as it is served on a published site. */
.invoiceWidget .pf-invoice-no {
    padding: 0;
    border: 0;
    background: none;
    font: inherit;
    font-weight: 600;
    color: #1a6ed8;
    cursor: pointer;
    text-align: left;
    white-space: nowrap;
}
.invoiceWidget .pf-invoice-no:hover,
.invoiceWidget .pf-invoice-no:focus {
    text-decoration: underline;
    outline: 0;
}
.invoiceWidget .pf-invoice-no:focus-visible {
    outline: 2px solid #1a6ed8;
    outline-offset: 2px;
}
/* On the selected row the grid paints its own ground, and a blue link on it is
 * the one thing that stops being readable. */
.invoiceWidget .ui-state-highlight .pf-invoice-no {
    color: inherit;
}

/* A cell is two lines: the value, and what qualifies it. The second line is
 * deliberately quiet — it is there to be read second, not scanned. */
.orders_customers .pf-ord-date,
.orders_customers .pf-ord-total-cell {
    color: #344054;
    line-height: 1.35;
}
.orders_customers .pf-ord-total-cell {
    font-weight: 600;
    white-space: nowrap;
}
.orders_customers .pf-ord-sub {
    color: #667085;
    font-size: 12px;
    line-height: 1.3;
}
.orders_customers .pf-ord-count {
    display: inline-block;
    min-width: 22px;
    padding: 1px 6px;
    border-radius: 10px;
    background-color: #f2f4f7;
    color: #344054;
    font-size: 12px;
    text-align: center;
}

/* MOBILE: one card per order in a single cell. The seven columns above are a
 * horizontal scrollbar on a 360px screen, so the same values are stacked. */
.orders_customers .pf-ord-card {
    display: block;
    padding: 6px 2px;
    line-height: 1.5;
}
.orders_customers .pf-ord-card .pf-order-no {
    display: block;
    margin-bottom: 4px;
    font-size: 15px;
}
.orders_customers .pf-ord-card-row span {
    display: inline-block;
    min-width: 68px;
    color: #667085;
    font-size: 12px;
}
.orders_customers .pf-ord-card-row b {
    color: #344054;
    font-weight: 500;
}

/* The payment-state pill, for the surfaces editor_uniform.css does not reach.
 * That sheet carries a fuller, colour-coded version scoped to .pf-owner-grid
 * and loads last in the editor, so this is the floor rather than a second
 * opinion: without it the value renders as a bare word in preview. */
.pf-state {
    display: inline-block;
    padding: 1px 8px;
    border: 1px solid #d0d5dd;
    border-radius: 10px;
    background-color: #f9fafb;
    color: #344054;
    font-size: 12px;
    line-height: 1.6;
    white-space: nowrap;
}

/* --- the order dialog ---------------------------------------------------
 * Opened from the order-number cell. It is the whole of what the old card list
 * showed inline behind a +/- toggle, which is why the list could be a page of
 * 20 orders and several hundred rows at once. */
.pf-order-dialog .ui-dialog-content {
    padding: 0;
}
/* The title bar is EMPTY on this dialog: the order number is the heading inside
 * the panel (.pf-ord-head-no), and carrying it in both put the same string twice
 * within 40px of itself. The bar stays — it is the drag handle and it holds the
 * close button — so it only needs to stop reserving a line of text it no longer
 * has. The accessible name is on the wrapper's aria-label instead. */
.pf-order-dialog .ui-dialog-titlebar {
    padding-top: 6px;
    padding-bottom: 6px;
}
.pf-order-dialog .ui-dialog-title {
    height: 0;
    margin: 0;
}
/* In the side panel (PF.ui.panel) the number is the panel's title and the panel pads its body. */
.pf-ord-panel .pf-ord-head-no { display: none; }
.pf-ord-panel .pf-ord-dlg { padding: 0; }
.pf-ord-dlg {
    padding: 4px 14px 14px;
    color: #344054;
    font-size: 13px;
    line-height: 1.5;
}
.pf-ord-head {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    flex-wrap: wrap;
    gap: 8px;
    padding: 10px 0;
    border-bottom: 1px solid #eaecf0;
}
.pf-ord-head-no {
    font-size: 15px;
    font-weight: 600;
    color: #101828;
}
.pf-ord-head-meta {
    color: #667085;
}
.pf-ord-sec {
    padding: 12px 0;
}
.pf-ord-sec h4 {
    margin: 0 0 8px;
    font-size: 12px;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: #667085;
}
.pf-ord-empty {
    color: #667085;
    font-style: italic;
}

/* One line item. The picture is a fixed 48px box so a mixed set of product
 * images still leaves the names on one left edge. */
.pf-ord-item {
    display: flex;
    align-items: flex-start;
    gap: 10px;
    padding: 8px 0;
    border-bottom: 1px solid #f2f4f7;
}
.pf-ord-item:last-child {
    border-bottom: 0;
}
.pf-ord-item-img {
    flex: 0 0 48px;
    width: 48px;
    height: 48px;
    display: flex;
    align-items: center;
    justify-content: center;
    overflow: hidden;
    border: 1px solid #eaecf0;
    border-radius: 6px;
    background-color: #fcfcfd;
    color: #98a2b3;
}
.pf-ord-item-img img {
    max-width: 100%;
    max-height: 100%;
}
.pf-ord-item-main {
    flex: 1 1 auto;
    min-width: 0;
}
.pf-ord-item-name {
    font-weight: 500;
    color: #101828;
}
.pf-ord-item-desc {
    color: #667085;
    font-size: 12px;
    /* Two lines, then stop: a product description can be a paragraph, and this
     * dialog is a summary of the order rather than of any one product. */
    max-height: 2.6em;
    overflow: hidden;
}
.pf-ord-item-money {
    flex: 0 0 auto;
    text-align: right;
    white-space: nowrap;
}
.pf-ord-item-line {
    font-weight: 600;
    color: #101828;
}
.pf-ord-item-unit {
    color: #667085;
    font-size: 12px;
}

.pf-ord-totals {
    border-top: 1px solid #eaecf0;
}
.pf-ord-total {
    display: flex;
    justify-content: space-between;
    gap: 16px;
    padding: 2px 0;
}
.pf-ord-total span {
    color: #667085;
}
.pf-ord-total-sum {
    margin-top: 6px;
    padding-top: 8px;
    border-top: 1px solid #eaecf0;
    font-size: 14px;
}
.pf-ord-total-sum b,
.pf-ord-total-sum span {
    color: #101828;
    font-weight: 600;
}

/* Customer and Delivery side by side on a desktop dialog, stacked when the
 * dialog is narrow — which is every mobile dialog, since it is opened at the
 * viewport width. */
.pf-ord-cols {
    display: flex;
    flex-wrap: wrap;
    gap: 0 24px;
    border-top: 1px solid #eaecf0;
}
.pf-ord-cols .pf-ord-sec {
    flex: 1 1 220px;
    min-width: 0;
}
.pf-ord-fact {
    display: flex;
    gap: 10px;
    padding: 2px 0;
}
.pf-ord-fact span {
    flex: 0 0 92px;
    color: #667085;
}
.pf-ord-fact b {
    font-weight: 500;
    /* An address or a transaction id is long and has no spaces to break on. */
    word-break: break-word;
    min-width: 0;
}


/* =========================================================================
 * The advanced-search panel — one look for the dialog form of it
 * =========================================================================
 * The panel opened from a datagrid's search icon (`.ui-dialog.search_product`,
 * which datagrid.advanced.search.js also tags `.pf-advsearch-dialog`) had never
 * been styled as a whole. Every control brought its own look: a jQuery UI 1.8
 * titlebar gradient, bare 25px checkboxes floated under a label that covered
 * them, a 0.8em grey slider from blue-theme.css, and a footer of one green and
 * one red gradient button that website-generator.css paints for `.save` and
 * `.delete` everywhere on a published site. The published restaurant menu is
 * where all of that shows at once.
 *
 * WHY HERE AND NOT IN editor_uniform.css — the same reason the Orders block
 * below gives: that sheet is loaded by header.tpl / headertemplates.tpl /
 * mobileheader.tpl only, and this panel's most visible home is a PUBLISHED site,
 * rendered through header_webgen.tpl. So: literal colours, no var(--pf-*)
 * (doc/EDITOR_STYLE_GUIDE.md rule 3). The values are the ones those tokens hold —
 * #0f172a ink, #344054 panel ink, #667085 soft, #e6e8ec line, #d7dbe0 control
 * line, #2a6b84 accent, #1f5265 accent-dark, #f1f9fc on-accent.
 *
 * THE ONE EXCEPTION, and why it does not break rule 3: every ACCENT below is
 * written `var(--pf-adv-accent, #2a6b84)`. The `--pf-adv-*` properties are not
 * editor tokens and are never defined in a stylesheet — datagrid.advanced.search.js
 * sets them INLINE on this one dialog, sampled from the site's own rendered cards,
 * so the panel wears the salon's green or the realtor's navy instead of an accent
 * from a different product. Where there is nothing to sample (the editor, the owner
 * screens, an empty grid) the property is simply absent and the fallback — the style
 * guide's own accent — is what paints. An undefined var() here therefore means "use
 * the editor's accent", not a dead rule.
 *
 * Every `!important` here answers a specific earlier declaration and says which.
 */

/* ---- the shell ---------------------------------------------------------- */
/* The site's font on every control, but only where datagrid.advanced.search.js found a site theme
 * (pfApplyPanelTheme adds .pf-site-themed): jportal3.css gives each div its own font, so inheriting
 * from the shell is not enough. Icon elements keep their glyph font. */
.ui-dialog.search_product.pf-site-themed *:not([class*="icon"]) {
    font-family: var(--pf-adv-font, inherit);
}
.ui-dialog.search_product {
    font-family: var(--pf-adv-font, inherit);
    border: 1px solid var(--pf-adv-line, #e6e8ec);
    border-radius: 12px;
    background: var(--pf-adv-bg, #fff);
    box-shadow: 0 16px 32px -12px rgba(16, 24, 40, .22);
    padding: 0;
    overflow: hidden;
}
.ui-dialog.search_product .ui-dialog-titlebar {
    /* ui-widget-header paints a gradient through background-image; a colour alone
     * does not remove it. */
    background-color: var(--pf-adv-bg, #fff);
    background-image: none;
    border: 0;
    border-bottom: 1px solid var(--pf-adv-line, #e6e8ec);
    border-radius: 0;
    padding: 12px 14px;
    margin: 0;
}
.ui-dialog.search_product .ui-dialog-title {
    font-size: 14px;
    font-weight: 600;
    color: var(--pf-adv-ink, #0f172a);
    margin: 0;
    float: none;
}
.ui-dialog.search_product .ui-dialog-titlebar-close {
    right: 10px;
    margin-top: -10px;
    border: 0;
    background: none;
}
.ui-dialog.search_product .adv-search-container {
    padding: 14px;
    box-sizing: border-box;
    background: var(--pf-adv-bg, #fff);
    border: 0;
}
/* The panel takes the height of its fields (the dialog is opened with
 * height:'auto' now). This is the ceiling, so a long category list scrolls inside
 * the panel rather than pushing the Find button off the bottom of the screen. */
/* Full-height sidebar: titlebar, fields, buttons — a flex column.
 *
 * The dialog is opened at the viewport's height (datagrid.advanced.search.js).
 * jQuery UI 1.8 sizes the CONTENT to that height and leaves the titlebar and the
 * button pane outside it, which is what put Find and Close below the fold with a
 * field of empty white above them. Making the dialog itself the column, with the
 * content the only part that grows and scrolls, keeps the buttons on screen and
 * gives the category list all the room that is left. */
.ui-dialog.search_product.pf-advsearch-dialog {
    /* !important on all four: jQuery UI writes `display`, `top` and `height` as INLINE
     * styles on this element every time the dialog opens or is resized, and inline beats
     * any stylesheet rule that is not !important. `height:auto` is what it writes for the
     * wrapper (UI 1.8 sizes the CONTENT instead), which is why setting the dialog's own
     * height option could never make the panel fill the viewport. */
    display: flex !important;
    flex-direction: column;
    top: 0 !important;
    height: 100vh !important;
    /* dvh tracks a phone's collapsing address bar; vh above is the fallback for
     * browsers that do not know it, and stays in effect there. */
    height: 100dvh !important;
    max-height: 100vh;
    box-sizing: border-box;
    border-radius: 0;          /* it is docked to the edge; a rounded edge would float */
}
/* CLOSING THE PANEL. `display: flex !important` above beats jQuery UI's inline
 * `display: block` on open -- and it also beat the inline `display: none` UI writes
 * on CLOSE, because an !important declaration outranks a non-important inline style.
 * So Close and the titlebar × ran, the widget really did close, and the panel stayed
 * on screen: "the close button does nothing", on every grid's search panel.
 *
 * The closed state therefore has to be !important too, and more specific than the
 * rule above (four classes to its three). datagrid.advanced.search.js adds the class
 * in the dialog's `close` callback and drops it in `open`, so it tracks the widget's
 * own state rather than guessing from an inline style. */
.ui-dialog.search_product.pf-advsearch-dialog.pf-advsearch-closed {
    display: none !important;
}
.ui-dialog.search_product.pf-advsearch-dialog .ui-dialog-titlebar,
.ui-dialog.search_product.pf-advsearch-dialog .ui-dialog-buttonpane {
    flex: 0 0 auto;
}
.ui-dialog.search_product .adv-search-container {
    /* !important answers jQuery UI, which writes height/max-height INLINE on the
     * content element from the dialog's own height option — inline beats any
     * stylesheet rule that is not !important, and that fixed height is exactly what
     * stops the column from distributing the space. */
    flex: 1 1 auto !important;
    height: auto !important;
    max-height: none !important;
    min-height: 0 !important;
    overflow-y: auto;
    /* Nothing in the panel is meant to scroll sideways. Without this the fields
     * overrun their column by a pixel or two and the panel grows a full-width
     * horizontal scrollbar between the last category and the footer. */
    overflow-x: hidden;
}
/* The category list is the one part worth giving the slack to, so it no longer
 * carries a max-height of its own — the panel scrolls as one. */
.ui-dialog.search_product .adv_category_box:first-child {
    margin-top: 0;
}

/* ---- field labels and text inputs --------------------------------------- *
 *
 * THE FIELD LABEL IS THE BOOKING DESK'S FIELD LABEL. The New booking panel
 * (js/widgets/searchBookingOwnerPages.js, `.pfa-addf label` / `.pfa-lbl3`) had
 * already settled what a field label looks like on an owner screen: 11px,
 * uppercase, .06em tracking, muted -- a caption over its control rather than a
 * second line of content competing with it. This panel sits beside those screens
 * and was still drawing 12px/600 near-black sentence case, which reads as a
 * heading and gives each field the same weight as the grid behind it.
 *
 * THE FIELD IS THE ADD-RESERVATION FIELD. `js/widgets/reservationsOwnerPages.js`
 * (`.pfv-a-grid label` / `.pfv-a-grid input`) is the newest form in the product and
 * the one this panel is now measured against: a 13px #334155 label in SENTENCE
 * case, 3px of air, then a self-sizing box with 5px/8px padding, a #d3d8e0 edge and
 * an 8px radius. Everything here is that form's, so a reader moving between the two
 * is not asked to learn a second idea of what a field looks like.
 *
 * WHAT WENT: 11px uppercase at .06em, and then 13px uppercase. A whole column of
 * capitals is a shout, and tracking them apart is a display treatment doing display
 * work on a filter panel -- it made five ordinary words (Name, Email, Phone, Status,
 * Date Range) read as five headings with forms attached. Sentence case at 400 is
 * what the rest of the product writes a field name in.
 *
 * The ink is #334155 and not the cell's #0f172a: in THIS form the label is the
 * quieter half, because what the owner is reading for is the value they are about
 * to type. The cell's size and family stay -- the family is not stated at all, it is
 * inherited from the panel, which is Inter in the editor (css/editor_uniform.css
 * names it on `.pf-owner-search`) and the site's own face on a published site, where
 * this sheet also lands.
 *
 * The gap under it is 3px, exactly the reservation field's `margin-top`, and the
 * label's own 1.45 leading is the rest of what you see. A caption belongs to the
 * control under it; the panel's old 6px plus that leading put it nearer to the field
 * ABOVE, and the eye had to pair them by reading rather than by seeing.
 *
 * EVERY panel, not just the dialog. This was scoped `.ui-dialog.search_product`,
 * which is stamped on every search DIALOG -- but a grid configured with
 * `inline_search` renders the same markup into a `<td>` beside the rows and never
 * becomes a dialog at all, so those panels kept the old 13px/600 label. The panel
 * is one control and gets one look.
 *
 * Only the labels that head a FIELD. The `td.ui-widget-content >` chain is what
 * keeps this off `.adv_category_box` / `.pnl-h` / `.control` labels, which are the
 * text beside a checkbox -- content, not a caption.
 *
 * Literals, not var(--pf-*) -- rule 3 of doc/EDITOR_STYLE_GUIDE.md, because this
 * sheet is loaded by header_webgen.tpl and no token is defined there. */
.adv-search-container td.ui-widget-content > .advsearch-field-label {
    font-size: 13px;
    font-weight: 400;
    line-height: 1.45;
    color: var(--pf-adv-label, #334155);
    /* Stated, not omitted: the rule this one replaces set both, and the generic
     * `.adv-search-container .advsearch-field-label` above still sets 600. */
    letter-spacing: normal;
    text-transform: none;
    margin-bottom: 3px;
    /* jportal2.css:3663 adds `padding-bottom: 5px` to every search_product label. */
    padding: 0;
}
/* The caption's text arrives as the column's `name`, and the widgets write it as an
 * inline-block <div> with its own inline `padding-bottom: 4px` (Orders, Invoices) or
 * `padding-top: 6px` (Invoices). Stacked with the label's 5px + 3px that put 15px
 * between a caption and its field -- five times the Add-reservation form's 3px.
 * Block, so it sits on no extra line box; !important, because only that beats an
 * inline style. The 3px margin above is then the one gap. :only-child, because
 * coupons.js composes a label of three divs with an inline %/$ toggle in the middle,
 * which a block would break onto separate lines. */
.adv-search-container td.ui-widget-content > .advsearch-field-label > div:only-child {
    display: block !important;
    padding-top: 0 !important;
    padding-bottom: 0 !important;
}
/* A field label with no text (the meal-type row) must not leave a 6px gap and a
 * blank line above its control. */
.ui-dialog.search_product .advsearch-field-label:empty {
    display: none;
}
/* The box, from the same form. `height: auto` and not a pinned 32px: the field is
 * sized by its own padding and line, so it stays right when the panel's type
 * changes and when a phone's 16px minimum kicks in. #d3d8e0 / 8px / 5px 8px are
 * the reservation field's; 13px and #0f172a are the grid cell's, which is what the
 * value in this box is going to be matched against.
 *
 * Not scoped to `.ui-dialog.search_product` any more, for the reason the label
 * above gives: a grid configured with `inline_search` never becomes a dialog. */
.adv-search-container td.ui-widget-content input[type="text"],
.adv-search-container td.ui-widget-content input[type="number"],
.adv-search-container td.ui-widget-content input[type="email"],
.adv-search-container td.ui-widget-content input[type="tel"],
.adv-search-container td.ui-widget-content input[type="date"],
.adv-search-container td.ui-widget-content select {
    height: auto;
    box-sizing: border-box;
    border: 1px solid var(--pf-adv-control, #d3d8e0);
    border-radius: var(--pf-adv-radius, 8px);
    padding: 5px 8px;
    font-size: 13px;
    line-height: 1.45;
    color: var(--pf-adv-ink, #0f172a);
    background: var(--pf-adv-field, #fff);
}
/* A <select> brings its own arrow and its own idea of a minimum height; the two
 * rules are separate so the box above stays one statement about one shape. */
.adv-search-container td.ui-widget-content select {
    width: 100%;
    padding-right: 4px;
}
/* The same box, at a weight that beats css/jportal2.css:3649, which pins
 * `border: 1px solid #dee2e6; color: #777` on exactly this input with (0,4,2) -- one
 * class more than the rule above can reach. Every search panel now carries
 * `search_product` (datagrid.advanced.search.js stamps it on open), so that rule
 * reaches all of them and is what kept the typed value grey while the label above it
 * and the rows behind it were near-black. Equal specificity, and this sheet is loaded
 * AFTER that one (header.tpl:88 vs _css_core.tpl:56), so order decides it. */
.search_product .adv-search-container td.ui-widget-content input[type="text"],
.search_product.adv-search-container td.ui-widget-content input[type="text"] {
    border: 1px solid var(--pf-adv-control, #d3d8e0);
    color: var(--pf-adv-ink, #0f172a);
}
/* And its label: the same sheet at :3658 pins 14px/#202124 on every
 * `.advsearch-field-label` at (0,2,0) -- which loses to the field-label rule above
 * (0,3,1) -- but the `.search_product` prefix makes it (0,3,0) for the panels that
 * carry the class, and that is a tie the FILE ORDER settles, not the selector. Stated
 * here so the two cannot silently swap places. */
.search_product .adv-search-container td.ui-widget-content > .advsearch-field-label,
.search_product.adv-search-container td.ui-widget-content > .advsearch-field-label {
    font-size: 13px;
    line-height: 1.45;
    font-weight: 400;
    color: var(--pf-adv-label, #334155);
}
.adv-search-container td.ui-widget-content input[type="text"]:focus,
.adv-search-container td.ui-widget-content input[type="number"]:focus,
.adv-search-container td.ui-widget-content input[type="email"]:focus,
.adv-search-container td.ui-widget-content input[type="tel"]:focus,
.adv-search-container td.ui-widget-content input[type="date"]:focus,
.adv-search-container td.ui-widget-content select:focus {
    outline: none;
    border-color: var(--pf-adv-accent, #2a6b84);
    /* 2px, not 3. On the two small number boxes in the From/To row a 3px ring is a
     * fifth of the box's own height, so the focused one read as physically bigger
     * and rounder than its twin beside it. */
    box-shadow: 0 0 0 2px var(--pf-adv-accent-ring, rgba(147, 195, 217, .45));
}
/* The spinner belongs to the field, so it is left on — but Chrome only reveals it on
 * hover/focus and reserves no room for it, which shoves a 3-digit price against the
 * arrows. This is the room. */
.adv-search-container td.ui-widget-content input[type="number"] {
    padding-right: 4px;
}

/* ---- the meal-type row (Breakfast / Lunch / Dinner) --------------------- *
 * Rendered by the `restautant_menu_opts` formatter as loose spans. One
 * segmented control: shared edges, no double borders, accent for the chosen one. */
.ui-dialog.search_product .notification-opt {
    display: flex;
    border: 1px solid var(--pf-adv-control, #d7dbe0);
    border-radius: var(--pf-adv-radius, 8px);
    overflow: hidden;
    box-sizing: border-box;
}
.ui-dialog.search_product .notification-opt .align {
    flex: 1 1 0;
    min-width: 0;
    text-align: center;
    padding: 0 8px;
    line-height: 30px;
    font-size: 13px;
    color: var(--pf-adv-label, #344054);
    cursor: pointer;
    /* blue-theme.css paints `.toolbaredit .selected, .ui-slider-handle, …` and a
     * broad button rule with !important gradients; these two answer those. */
    background-color: var(--pf-adv-field, #fff) !important;
    background-image: none !important;
    border-right: 1px solid var(--pf-adv-control, #d7dbe0);
    transition: background-color .15s ease, color .15s ease;
}
.ui-dialog.search_product .notification-opt .align:last-child {
    border-right: 0;
}
.ui-dialog.search_product .notification-opt .align:hover {
    background-color: var(--pf-adv-hover, #f6f7f9) !important;
}
.ui-dialog.search_product .notification-opt .align.selected,
.ui-dialog.search_product .notification-opt .align.selected:hover {
    background-color: var(--pf-adv-accent, #2a6b84) !important;
    background-image: none !important;
    color: var(--pf-adv-accent-ink, #f1f9fc);
}
.ui-dialog.search_product .notification-opt .align.selected span {
    color: var(--pf-adv-accent-ink, #f1f9fc);
}

/* ---- the price range ---------------------------------------------------- *
 * TWO FIELDS SIDE BY SIDE, each with its label over its own box -- the shape every
 * other field in this panel has, and the Add-reservation dialog's before that.
 *
 * It was one flex LINE: label, box, label, box. Three things went wrong with that in
 * a 250px column. "To", sitting between the two boxes, read as a separator rather
 * than as the caption of the box after it. The two boxes shared whatever the labels
 * left, so a seven-digit bound clipped inside its own field ("1000000" as
 * "100000("). And the labels were 12px #667085 while every other caption in the
 * panel is 13px #334155 -- a third label style in one column.
 *
 * Not scoped to `.ui-dialog.search_product` any anymore: a grid configured with
 * `inline_search` renders the same markup and never becomes a dialog. */
.adv-search-container .pf-range-table {
    width: 100%;
    table-layout: fixed;
    /* A table's default 2px spacing + 1px cell padding put From/To 3px further
     * under "Order total" than every other field sits under its caption. */
    border-spacing: 0;
}
.adv-search-container .pf-range-row {
    display: flex;
    align-items: flex-end;
    gap: 10px;
    padding: 0;
}
/* One bound. `1 1 0` and `min-width: 0`, so the pair is always two equal halves and
 * neither can be pushed out of the panel by a long number. */
.adv-search-container .pf-range-row > .pf-range-f {
    display: flex;
    flex-direction: column;
    flex: 1 1 0;
    min-width: 0;
}
/* The panel's field label, to the pixel -- see the .advsearch-field-label rule. It
 * was four inline `style=` attributes in the markup, which no stylesheet can answer,
 * and that is why these two never followed the rest of the panel. */
.adv-search-container .pf-range-row label.pf-range-lbl {
    font-size: 13px;
    font-weight: 400;
    line-height: 1.45;
    color: var(--pf-adv-label, #334155);
    white-space: nowrap;
    margin: 0 0 3px 0;
    padding: 0;
}
/* The box is the panel's box: the width, the float and the 80px ceiling are all
 * being UNDONE here (`.adv-search-container td.ui-widget-content input.min-value`
 * further up this sheet floats it left, pads it 5px/0 and caps it at 80px), and
 * everything else -- edge, radius, padding, type -- comes from the shared input
 * rule. `height: auto` and no text-align: a number box that sizes itself the way
 * the field above it does cannot end up a different height from its own twin, which
 * is what the old pinned padding-plus-focus-ring did. */
.adv-search-container td.ui-widget-content .pf-range-f input.min-value,
.adv-search-container td.ui-widget-content .pf-range-f input.max-value {
    display: block;
    width: 100%;
    min-width: 0;
    max-width: none;
    height: auto;
    box-sizing: border-box;
    padding: 5px 4px 5px 8px;
    float: none;
    margin: 0;
}
.ui-dialog.search_product .adv-slider {
    /* The markup gives the track a 2px top border and 0 height, so the "track" is
     * that border. Drawn as a real 4px rail instead. */
    height: 4px !important;
    border: 0 !important;
    border-radius: 999px;
    background-color: #e6e8ec !important;
    background-image: none !important;
    top: 6px;
}
.ui-dialog.search_product .adv-slider .ui-slider-range {
    background-color: var(--pf-adv-accent, #2a6b84) !important;
    background-image: none !important;
    border: 0 !important;
    border-radius: 999px;
    box-shadow: none;
}
.ui-dialog.search_product .adv-slider .ui-slider-handle {
    width: 14px;
    height: 14px;
    top: -5px;
    margin-top: 0 !important;
    margin-left: -7px;
    border-radius: 50%;
    border: 2px solid var(--pf-adv-accent, #2a6b84) !important;
    /* blue-theme.css:  `.ui-slider .ui-slider-handle { background-color:#aaa !important }`
     * plus a grey gradient — both have to be answered to get a white knob. */
    background-color: #fff !important;
    background-image: none !important;
    box-shadow: 0 1px 2px rgba(16, 24, 40, .18);
    cursor: pointer;
}

/* ---- the category list -------------------------------------------------- *
 * THE HIT-TARGET FIX. `.adv_category_box.border_row .pnl-h .advsearch-field-label`
 * was `display:block; position:relative; padding-left:25px` next to a
 * `float:left` checkbox — a positioned block box whose left edge is the SAME x as
 * the float it is supposed to sit beside, so it painted straight over the box and
 * swallowed every click aimed at it. elementFromPoint() on the checkbox returned
 * the label. The row is a flex row now: the box and the text are siblings on one
 * line, neither covers the other, and (with the `for=` the renderer emits) the
 * whole row toggles. */
.adv_category_box.border_row .pnl-h {
    display: flex;
    align-items: center;
    gap: 10px;
    border: 0;
    border-bottom: 1px solid var(--pf-adv-line, #e6e8ec);
    padding: 0 4px;
    min-height: 36px;
    cursor: pointer;
    transition: background-color .15s ease;
}
.adv_category_box.border_row:first-child .pnl-h {
    border-top: 1px solid var(--pf-adv-line, #e6e8ec);
}
.adv-search-container .adv_category_box.border_row .pnl-h:hover {
    background: var(--pf-adv-hover, #f6f7f9);
}
.adv_category_box.border_row .pnl-h .category-inp {
    float: none;
    flex: 0 0 auto;
    width: 15px;
    height: 15px;
    margin: 0;
    /* Paints the tick in the panel's accent wherever the browser supports it, and
     * is simply ignored where it does not — no custom indicator to keep in sync. */
    accent-color: var(--pf-adv-accent, #2a6b84);
    cursor: pointer;
}
.adv_category_box.border_row .pnl-h .advsearch-field-label {
    /* Undoes the overlay geometry named above. */
    position: static;
    display: block;
    float: none;
    flex: 1 1 auto;
    min-width: 0;
    padding: 0;
    margin: 0;
    font-size: 13px;
    font-weight: 400;
    line-height: 18px;
    color: var(--pf-adv-label, #344054);
    cursor: pointer;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}
.adv_category_box.border_row .sbc-elm {
    display: flex;
    align-items: center;
    gap: 10px;
    padding: 4px 4px 4px 26px;
    cursor: pointer;
}
.adv_category_box.border_row .sbc-elm .chkb {
    float: none;
    flex: 0 0 auto;
    margin: 0;
    accent-color: var(--pf-adv-accent, #2a6b84);
}
.adv_category_box.border_row .sbc-elm .adv_subcategory_label {
    float: none;
    flex: 1 1 auto;
    min-width: 0;
    margin: 0;
    max-width: none;
    font-size: 13px;
    color: var(--pf-adv-label, #344054);
    cursor: pointer;
}

/* ---- the category list, `fixed-category` flavour ------------------------ *
 * The other renderer in datagrid.advanced.search.js draws its OWN checkbox: the
 * real <input> is `opacity:0; z-index:-1` and a `.control__indicator` div is
 * painted where it would have been (datagrid.css:948 above). That is what the
 * Appointment and Coupons panels use, and it came out a hard cyan — #2aa1c0
 * checked, #0e647d on hover — that belongs to no palette on either page.
 *
 * Same accent, same box, same row rhythm as the `border_row` flavour above, so the
 * two renderers finally read as one control. The indicator keeps a visible edge when
 * unchecked: as a bare #e6e6e6 fill it read as a disabled control rather than an
 * empty one. */
.ui-dialog.search_product .adv-search-container .adv_category_box {
    border-bottom: 1px solid var(--pf-adv-line, #e6e8ec);
}
.ui-dialog.search_product .adv-search-container .control.pnl-h {
    padding: 0 4px 0 26px;
    min-height: 36px;
    display: flex;
    align-items: center;
    border: 0;
    transition: background-color .15s ease;
}
.ui-dialog.search_product .adv-search-container .control.pnl-h:hover {
    background: var(--pf-adv-hover, #f6f7f9);
}
.ui-dialog.search_product .adv-search-container .control.sbc-elm {
    padding: 4px 4px 4px 44px;
    display: flex;
    align-items: center;
    min-height: 28px;
    border: 0;
}
.ui-dialog.search_product .adv-search-container .control .advsearch-field-label,
.ui-dialog.search_product .adv-search-container .control .adv_subcategory_label {
    font-size: 13px;
    font-weight: 400;
    color: var(--pf-adv-label, #344054);
    margin: 0;
    max-width: none;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}
.ui-dialog.search_product .adv-search-container .control__indicator {
    top: 50%;
    transform: translateY(-50%);
    left: 4px;
    width: 16px;
    height: 16px;
    background: var(--pf-adv-field, #fff);
    border: 1px solid var(--pf-adv-control, #d7dbe0);
    border-radius: 4px;
    box-sizing: border-box;
    transition: background-color .15s ease, border-color .15s ease;
}
.ui-dialog.search_product .adv-search-container .control.sbc-elm .control__indicator {
    left: 22px;
}
.ui-dialog.search_product .adv-search-container .control:hover input ~ .control__indicator,
.ui-dialog.search_product .adv-search-container .control input:focus ~ .control__indicator {
    background: var(--pf-adv-field, #fff);
    border-color: #98a2b3;
}
.ui-dialog.search_product .adv-search-container .control input:checked ~ .control__indicator,
.ui-dialog.search_product .adv-search-container .control:hover input:not([disabled]):checked ~ .control__indicator,
.ui-dialog.search_product .adv-search-container .control input:checked:focus ~ .control__indicator {
    background: var(--pf-adv-accent, #2a6b84);
    border-color: var(--pf-adv-accent-dark, #1f5265);
}
/* The tick is drawn as two borders of a rotated box, so it takes the accent's ink
 * through border-color — not `color`. */
.ui-dialog.search_product .adv-search-container .control--checkbox .control__indicator:after {
    left: 5px;
    top: 2px;
    width: 3px;
    height: 7px;
    border-color: var(--pf-adv-accent-ink, #f1f9fc);
}

/* ---- the footer --------------------------------------------------------- *
 * Find is the primary action and Close is neutral, per
 * doc/EDITOR_STYLE_GUIDE.md §3.3. On a PUBLISHED site neither class means that:
 * website-generator.css:10038 paints `.ui-button.ui-state-default.save` a green
 * gradient and :9975 paints `.delete` a red one, both with !important on
 * background-image — which is why the panel's footer read as Save/Delete rather
 * than Find/Close. These answer exactly those two rules. */
.ui-dialog.search_product .ui-dialog-buttonpane {
    border: 0;
    border-top: 1px solid var(--pf-adv-line, #e6e8ec);
    margin: 0;
    padding: 10px 14px;
    background: var(--pf-adv-bg, #fff);
}
.ui-dialog.search_product .ui-dialog-buttonpane .ui-dialog-buttonset {
    float: right;
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button {
    height: 30px;
    padding: 0;
    margin: 0 0 0 8px;
    border-radius: var(--pf-adv-radius, 8px);
    font-size: 13px;
    font-weight: 600;
    cursor: pointer;
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button .ui-button-text {
    padding: 0 14px;
    line-height: 28px;
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.save {
    background-color: var(--pf-adv-accent, #2a6b84);
    background-image: none !important;   /* website-generator.css:10038's green gradient */
    border: 1px solid var(--pf-adv-accent-dark, #1f5265);
    color: var(--pf-adv-accent-ink, #f1f9fc);
    /* !important answers website-generator.css, whose focused .ui-button.ui-state-default rule paints the
     * edge #10b981 !important — a green ring round the site's own accent on every open (Find is focused) */
    border-color: var(--pf-adv-accent-dark, #1f5265) !important;
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.save:hover,
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.save.ui-state-hover {
    background-color: var(--pf-adv-accent-dark, #1f5265);
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.delete {
    background-color: var(--pf-adv-bg, #fff);
    background-image: none !important;   /* website-generator.css:9975's red gradient */
    border: 1px solid var(--pf-adv-control, #d7dbe0);
    /* Same rule sets `border-color: #ef4444 #dc2626 … !important`, so the edge
     * stayed red over a white ground until this matched it. */
    border-color: var(--pf-adv-control, #d7dbe0) !important;
    color: var(--pf-adv-label, #344054);
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.delete:hover,
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.delete.ui-state-hover {
    background-color: var(--pf-adv-hover, #f6f7f9);
}
/* jQuery UI's .button({icons:{primary:…}}) positions .ui-icon ABSOLUTELY at
 * left:.5em and pads the label to clear it — padding this rule sets itself, so
 * the tile landed on top of the "F". The tile is also a #454545 sprite, invisible
 * on the accent ground. The word carries the button on its own; the glyph goes. */
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button .ui-icon {
    display: none;
}
.ui-dialog.search_product .ui-dialog-buttonpane button.ui-button.ui-button-text-icon-primary .ui-button-text {
    /* Undo the room jQuery UI reserved for the icon just hidden. */
    padding: 0 14px;
}

/* The titlebar X is painted red by an earlier sheet's close-button rule; in a
 * panel whose only destructive-looking control should be nothing at all, it is a
 * neutral glyph. */
.ui-dialog.search_product .ui-dialog-titlebar-close .ui-icon {
    background-image: url(images/ui-icons_454545_256x240.png);
}

/* The empty result — the block view's (DataGrid.class.js, the async_load branch)
 * and the Service Manager's `#emptyGrid` (jqmarket-dev.js), which are the same
 * statement made in two places.
 *
 * A grid that drew nothing at all read as a broken filter, which is what the
 * restaurant menu's demo-data fallback existed to hide. Centred, quiet, and it
 * reserves enough height that the page below does not jump up to meet it.
 *
 * min-height, not a percentage: the Service Manager's version is appended into a
 * container it has just emptied, whose height therefore comes from its content.
 * `height: 99%` of that resolved to 4px and the message was invisible. */
.pf-dg-empty {
    display: block;
    box-sizing: border-box;
    min-height: 180px;
    padding: 64px 16px;
    text-align: center;
    font-size: 15px;
    color: #667085;
    background: transparent;
    border: 0;
}

/* ------------------------------------------------------------------------------------------
 * Catalogue card call-to-action: reachable by finger, visible to a keyboard.
 *
 * This sheet is the one that reaches PUBLISHED sites (header.tpl:88), which is why the rules
 * live here rather than in editor_uniform.css.
 *
 * WHY !important, which this file otherwise avoids.
 * A card's button carries its size as an INLINE style, written into the block template's
 * __css by the template generator (scripts/service_block_templates.py) and applied by
 * coreListing. A stylesheet declaration cannot out-specify an inline one; an author
 * !important can, and it is the only lever that reaches the sites already carrying a stored
 * product_template - which is every live site, since a template is copied into the widget at
 * creation and never re-read. The templates themselves are being re-cut to state 44px; this
 * is what covers everything created before that.
 *
 * Measured on a live salon menu before this rule: 105x34 on desktop, 123x40 on a phone,
 * against the 44x44 minimum. Only the coarse-pointer case is corrected - a mouse does not
 * need the extra 4px and widening every desk button would change layouts for no gain.
 *
 * Rows render height:auto at runtime (product_listing_render.js), so a taller button grows
 * the card rather than being clipped by it.
 */
@media (pointer: coarse) {
    .funding-tiles .cart_button,
    .funding-tiles button[idrel] {
        min-height: 44px !important;
    }
}

/* A visible keyboard focus ring. The card's button was the only focusable thing in the tile
 * and it showed nothing at all when focused, so a keyboard user could not tell which card
 * they were on. :focus-visible, not :focus, so a mouse click does not draw it. No colour is
 * taken from the site theme on purpose - the ring has to stay visible against whatever
 * surface the theme painted, and currentColor would vanish on a button whose text matches
 * its own background. */
.funding-tiles .cart_button:focus-visible,
.funding-tiles button[idrel]:focus-visible,
.funding-tiles a.block-photo:focus-visible {
    outline: 2px solid #1a73e8;
    outline-offset: 2px;
    box-shadow: 0 0 0 4px rgba(26, 115, 232, 0.25);
}

/* =========================================================================
 * ORDERS / INVOICES — Phase 1 of the redesign (2026-09-24).
 * Tiles, plain-word tabs, a next-step button per row, an Undo toast, and the
 * action forms in the detail panel. Here rather than editor_uniform.css
 * because the owner screens also render on the preview surfaces, which that
 * sheet never reaches (see .pf-owner-toolbar-band above).
 * ======================================================================= */
.pf-ob-strip {
    display: flex;
    flex-direction: column;
    gap: 10px;
    padding: 0 2px 10px;
    color: #344054;
    font-size: 13px;
}
.pf-ob-tiles {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(170px, 1fr));
    gap: 10px;
}
.pf-ob-tile {
    display: flex;
    flex-direction: column;
    align-items: flex-start;
    gap: 2px;
    min-width: 0;
    padding: 10px 14px;
    border: 1px solid #e4e7ec;
    border-radius: 10px;
    background: #fff;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}
button.pf-ob-tile:hover { border-color: #b8c4d0; background: #fafbfc; }
button.pf-ob-tile:focus-visible { outline: 2px solid var(--pf-accent, #2a6b84); outline-offset: 2px; }
.pf-ob-tile.is-sales { cursor: default; }
.pf-ob-tl { font-size: 12px; color: #667085; }
.pf-ob-tile b { font-size: 20px; font-weight: 600; color: #101828; line-height: 1.25; }
.pf-ob-tile em { font-style: normal; font-size: 12px; color: #667085; }
.pf-ob-tile.is-accent b { color: var(--pf-accent, #2a6b84); }
.pf-ob-tile.is-warn b { color: #b54708; }
.pf-ob-tile.is-bad b { color: #b42318; }
.pf-ob-period { display: inline-flex; gap: 4px; margin-top: 4px; flex-wrap: wrap; }
.pf-ob-period button {
    padding: 1px 8px;
    border: 1px solid #d0d5dd;
    border-radius: 999px;
    background: #fff;
    color: #475467;
    font: inherit;
    font-size: 11px;
    cursor: pointer;
}
.pf-ob-period button[aria-pressed="true"] {
    border-color: var(--pf-accent, #2a6b84);
    background: var(--pf-accent-fill, #d9eaf3);
    color: var(--pf-accent-dark, #1f5265);
}
.pf-ob-bar { display: flex; align-items: center; justify-content: space-between; gap: 10px; flex-wrap: wrap; }
.pf-ob-tabs { display: inline-flex; gap: 2px; padding: 3px; border-radius: 9px; background: #f2f4f7; flex-wrap: wrap; }
.pf-ob-tab {
    padding: 5px 14px;
    border: 0;
    border-radius: 7px;
    background: transparent;
    color: #475467;
    font: inherit;
    font-weight: 500;
    cursor: pointer;
}
.pf-ob-tab[aria-selected="true"] { background: #fff; color: #101828; box-shadow: 0 1px 2px rgba(16, 24, 40, 0.1); }
.pf-ob-tab:focus-visible { outline: 2px solid var(--pf-accent, #2a6b84); outline-offset: 1px; }
.pf-ob-n { color: #667085; font-weight: 400; }
.pf-ob-tool {
    padding: 5px 12px;
    border: 1px solid #d0d5dd;
    border-radius: 8px;
    background: #fff;
    color: #344054;
    font: inherit;
    cursor: pointer;
}
.pf-ob-hint { font-size: 12px; color: #667085; min-height: 0; }
.pf-ob-hint:empty { display: none; }

/* The next-step button on a row: the one thing to do with this order now. */
.pf-ord-step {
    padding: 4px 12px;
    border: 1px solid var(--pf-accent, #2a6b84);
    border-radius: 7px;
    background: #fff;
    color: var(--pf-accent, #2a6b84);
    font: inherit;
    font-size: 12px;
    font-weight: 600;
    white-space: nowrap;
    cursor: pointer;
}
.pf-ord-step:hover { background: var(--pf-accent-fill, #d9eaf3); }

.pf-ob-toast {
    position: fixed;
    left: 50%;
    bottom: 24px;
    z-index: 100000;
    display: flex;
    align-items: center;
    gap: 14px;
    max-width: calc(100vw - 32px);
    padding: 10px 16px;
    border-radius: 10px;
    background: #1d2939;
    color: #fff;
    font-size: 13px;
    box-shadow: 0 8px 24px rgba(16, 24, 40, 0.25);
    transform: translateX(-50%);
}
.pf-ob-toast-undo {
    padding: 0;
    border: 0;
    background: none;
    color: #9fd3ea;
    font: inherit;
    font-weight: 600;
    cursor: pointer;
}

.pf-ob-empty { max-width: 460px; margin: 0 auto; padding: 16px; text-align: center; color: #475467; }
.pf-ob-empty-t { font-size: 17px; font-weight: 600; color: #101828; margin-bottom: 6px; }
.pf-ob-empty-s { font-size: 13px; margin-bottom: 12px; }
.pf-ob-check { list-style: none; margin: 0 0 14px; padding: 0; text-align: left; display: inline-block; }
.pf-ob-check li { padding: 4px 0; font-size: 13px; }
.pf-ob-check li span { display: inline-block; width: 18px; color: #98a2b3; }
.pf-ob-check li.is-done span { color: #1a6b3c; }
.pf-ob-check li.is-done { color: #667085; }

/* Detail panel: what the owner can do, above what the order says. */
.pf-ord-actions { display: flex; flex-direction: column; gap: 10px; padding: 12px 0; border-bottom: 1px solid #eaecf0; }
.pf-ord-act-t { font-weight: 600; color: #101828; margin-bottom: 4px; }
.pf-ord-act-f { display: flex; gap: 6px; flex-wrap: wrap; align-items: center; }
.pf-ord-act-h { font-size: 12px; color: #667085; margin-top: 4px; }
.pf-ord-in {
    min-width: 0;
    flex: 1 1 140px;
    padding: 6px 8px;
    border: 1px solid #d0d5dd;
    border-radius: 7px;
    font: inherit;
    color: #101828;
    background: #fff;
}
.pf-ord-in.is-money { flex: 0 1 110px; }
.pf-ord-btn {
    padding: 6px 14px;
    border: 1px solid #d0d5dd;
    border-radius: 7px;
    background: #fff;
    color: #344054;
    font: inherit;
    font-weight: 600;
    cursor: pointer;
    white-space: nowrap;
}
.pf-ord-btn.is-primary { border-color: var(--pf-accent, #2a6b84); background: var(--pf-accent, #2a6b84); color: #fff; }
.pf-ord-btn.is-danger { border-color: #d92d20; background: #fff; color: #b42318; }
.pf-ord-btn[disabled], .pf-ord-step[disabled] { opacity: 0.55; cursor: progress; }
.pf-ord-link {
    padding: 0;
    border: 0;
    background: none;
    color: #1a6ed8;
    font: inherit;
    cursor: pointer;
    text-decoration: underline;
}
.pf-ord-refund summary { cursor: pointer; font-weight: 600; color: #b42318; }
.pf-ord-refund[open] summary { margin-bottom: 6px; }
.pf-ord-msg:empty { display: none; }
.pf-ord-msg { font-size: 13px; color: #1a6b3c; }
.pf-ord-msg.is-bad { color: #b42318; }
.pf-ord-note div { white-space: pre-wrap; background: #fffbeb; border: 1px solid #fde68a; border-radius: 8px; padding: 8px 10px; }
.pf-ord-card-top { display: flex; align-items: center; justify-content: space-between; gap: 8px; flex-wrap: wrap; }
.pf-ord-card .pf-ord-step { margin-top: 8px; width: 100%; padding: 8px; }

/* The plain-word states. Scoped the same way as editor_uniform.css's pill so
 * these win over its neutral default in the grid, and unscoped for the panel. */
.pf-state[data-state="new"], .pf-state[data-state="sent"], .pf-state[data-state="viewed"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="new"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="sent"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="viewed"] {
    background-color: #eaf2fb; border-color: #bcd4f0; color: #1d4f8a;
}
.pf-state[data-state="preparing"], .pf-state[data-state="ready"], .pf-state[data-state="unpaid"],
.pf-state[data-state="part_paid"], .pf-state[data-state="not_sent"], .pf-state[data-state="draft"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="preparing"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="ready"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="unpaid"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="part_paid"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="not_sent"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="draft"] {
    background-color: #fdf4e3; border-color: #f2d59b; color: #8a5a08;
}
.pf-state[data-state="shipped"], .pf-state[data-state="completed"], .pf-state[data-state="paid"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="shipped"] {
    background-color: #e8f6ed; border-color: #b7e0c6; color: #1a6b3c;
}
.pf-state[data-state="overdue"], .pf-state[data-state="refunded"], .pf-state[data-state="cancelled"],
.pf-state[data-state="part_refunded"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="overdue"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="part_refunded"] {
    background-color: #fdecec; border-color: #f3bcbc; color: #a12424;
}
.pf-state[data-state="not_finished"], .pf-state[data-state="quote"], .pf-state[data-state="test"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="not_finished"],
.pf-owner-grid .ui-datagrid-main-table td .pf-state[data-state="quote"] {
    background-color: #f2f4f7; border-color: #d0d5dd; color: #475467;
}
@media (max-width: 600px) {
    .pf-ob-tiles { grid-template-columns: 1fr 1fr; }
    .pf-ob-tile.is-sales { grid-column: 1 / -1; }
    .pf-ob-tile b { font-size: 17px; }
}

/* Invoices: late dates, the actions cell, and the automatic-reminders dialog. */
.pf-inv-late, .pf-ord-sub.pf-inv-late { color: #b42318; font-weight: 600; }
.pf-inv-actions { display: flex; align-items: center; gap: 4px; flex-wrap: nowrap; }
.pf-inv-actions .pf-inv-remind { margin-right: 4px; }
.pf-ob-tool.is-on { border-color: #b7e0c6; background: #e8f6ed; color: #1a6b3c; }
.pf-inv-strip { padding-left: 8px; padding-right: 8px; }
.pf-dun { display: flex; flex-direction: column; gap: 6px; padding: 12px 16px; font-size: 13px; color: #344054; }
.pf-dun label { display: flex; align-items: center; gap: 8px; cursor: pointer; }
.pf-dun-on { font-weight: 600; color: #101828; }
.pf-dun-t { margin-top: 8px; font-weight: 600; color: #101828; }
.pf-dun-h { font-size: 12px; color: #667085; }
.pf-dun-warn { margin-top: 8px; padding: 8px 10px; border-radius: 8px; background: #fdf4e3; color: #8a5a08; font-size: 12px; }
.pf-dun select { padding: 6px 8px; border: 1px solid #d0d5dd; border-radius: 7px; font: inherit; }
/* Invoices keeps its own absolutely placed Search / + icons (jportal3.css) at top:10px;
 * the board starts below them. */
.invoiceWidget .pf-inv-strip { margin-top: 44px; }

/* Orders Phase 2: selection, bulk bar, customer card, activity feed. */
.pf-ord-nocell { display: flex; align-items: flex-start; gap: 8px; }
.pf-ord-sel { margin-top: 3px; width: 16px; height: 16px; cursor: pointer; }
.pf-ob-bulk { display: flex; align-items: center; gap: 8px; flex-wrap: wrap; padding: 8px 10px; border-radius: 9px; background: #eaf2fb; border: 1px solid #bcd4f0; }
.pf-ob-bulk-n { font-weight: 600; color: #1d4f8a; margin-right: 6px; }
.pf-ord-ship { margin-top: 6px; }
.pf-ord-cust-n { display: flex; gap: 14px; align-items: center; flex-wrap: wrap; }
.pf-ord-cust-n b { color: #101828; }
.pf-ord-ta { width: 100%; box-sizing: border-box; resize: vertical; margin-bottom: 6px; }
.pf-ord-feed .pf-ord-ev { padding: 6px 0 6px 12px; border-left: 2px solid #e4e7ec; margin-left: 4px; }
.pf-ord-ev-at { font-size: 11px; color: #667085; }
.pf-ord-ev.is-note { border-left-color: #fde68a; background: #fffbeb; }
.pf-ord-ev.is-message { border-left-color: #bcd4f0; }
.pf-ord-ev.is-payment { border-left-color: #b7e0c6; }
.pf-ord-ev.is-refund { border-left-color: #f3bcbc; }

/* Invoices Phase 2 */
.pf-inv-bar-r { display: inline-flex; gap: 8px; align-items: center; flex-wrap: wrap; }
.pf-inv-cards { display: flex; flex-direction: column; gap: 6px; }
.pf-inv-cards:empty { display: none; }
.pf-inv-card {
    display: flex; align-items: center; justify-content: space-between; gap: 10px;
    padding: 8px 12px; border: 1px solid #bcd4f0; border-radius: 9px; background: #eaf2fb;
    color: #1d4f8a; font: inherit; font-size: 13px; text-align: left; cursor: pointer;
}
.pf-inv-card b { font-weight: 600; }
.pf-inv-card span { white-space: nowrap; text-decoration: underline; }
.pf-inv-card.is-warn { border-color: #f2d59b; background: #fdf4e3; color: #8a5a08; }
.pf-inv-act { border-bottom: 1px solid #eaecf0; background: #fafbfc; font-size: 13px; color: #344054; }
.pf-inv-act-head { display: flex; align-items: center; justify-content: space-between; gap: 8px; padding: 6px 12px; flex-wrap: wrap; }
.pf-inv-act-toggle { padding: 0; border: 0; background: none; font: inherit; font-weight: 600; color: #101828; cursor: pointer; text-align: left; }
.pf-inv-act-tools { display: inline-flex; gap: 12px; flex-wrap: wrap; }
.pf-inv-act-cancel { color: #b42318; }
.pf-inv-act-body { max-height: 200px; overflow: auto; padding: 0 12px 8px; }
.pf-inv-feed { list-style: none; margin: 0; padding: 0; }
.pf-inv-feed li { padding: 4px 0; border-top: 1px solid #f2f4f7; }
.pf-inv-feed li span { display: inline-block; min-width: 150px; color: #667085; font-size: 12px; }
.pf-inv-feed li[data-kind="payment"] { color: #1a6b3c; }
.pf-inv-feed li[data-kind="refund"], .pf-inv-feed li[data-kind="cancelled"] { color: #a12424; }
/* Pay by phone (QR): the invoice's pay link, scanned by a customer at the desk (invoiceWidget _showPayQr). */
.pf-inv-qr { position: fixed; inset: 0; z-index: 99990; display: flex; align-items: center; justify-content: center; padding: 16px; background: rgba(16, 24, 40, .55); }
.pf-inv-qr-box { width: 100%; max-width: 340px; box-sizing: border-box; padding: 20px; border-radius: 14px; background: #fff; text-align: center; box-shadow: 0 20px 40px rgba(16, 24, 40, .25); }
.pf-inv-qr-box h3 { margin: 0 0 4px; font-size: 18px; color: #101828; }
.pf-inv-qr-code { display: inline-block; margin: 12px 0; padding: 10px; border: 1px solid #eaecf0; border-radius: 10px; background: #fff; word-break: break-all; font-size: 12px; }
.pf-inv-qr-code img, .pf-inv-qr-code canvas { display: block; max-width: 100%; height: auto; }
.pf-inv-qr-acts { display: flex; flex-wrap: wrap; gap: 12px; align-items: center; justify-content: center; }
/* Other ways to pay (invoiceWidget _openManualPay / _claimHtml): the owner's settings and the customers' reports. */
.pf-mp-set-m { padding: 10px 0 12px; border-top: 1px solid #eaecf0; }
.pf-mp-set-m.pf-mp-set-bad { background: #fef3f2; margin: 0 -8px; padding: 10px 8px 12px; border-radius: 8px; }
.pf-mp-set-f, .pf-dun label.pf-mp-set-f { display: block; margin: 8px 0 0; }   /* the label above its box: .pf-dun label is a flex row */
.pf-mp-set-f span { display: block; font-size: 13px; color: #475467; margin-bottom: 4px; }
.pf-mp-set-f input, .pf-mp-set-f textarea, .pf-mp-set-f select { width: 100%; box-sizing: border-box; padding: 8px 10px; border: 1px solid #d0d5dd; border-radius: 8px; font: inherit; }
/* phase 4: one method's QR picture (Upload / Replace / Remove, saved at once) */
.pf-mp-set-qr { margin: 10px 0 0; }
.pf-mp-set-qr-k { display: block; font-size: 13px; color: #475467; margin-bottom: 6px; }
.pf-mp-set-qr-row { display: flex; flex-wrap: wrap; gap: 8px 10px; align-items: center; }
.pf-mp-set-qr-img { width: 96px; height: 96px; object-fit: contain; border: 1px solid #eaecf0; border-radius: 8px; background: #fff; }
.pf-mp-set-qr-up { cursor: pointer; }
/* Website → Payment and Notification → Zelle / Venmo (main.js _mpWebForm): short label + "?" whose tooltip shows on
   hover, tap (focus) or Tab. The tip is the button's data-tip; its aria-label says the same to a screen reader. */
.pf-mp-k { display: flex !important; align-items: center; gap: 6px; }
.pf-dun label.pf-mp-k-l { display: inline; cursor: default; }
.pf-mp-chk { display: flex; align-items: center; gap: 6px; margin: 2px 0 4px; }
.pf-mp-help { position: relative; flex: none; display: inline-block; width: auto; height: auto; padding: 0 2px; margin: 0;
  border: 0; background: none; box-shadow: none; color: #344054; font: 700 13px/1 Arial, Helvetica, sans-serif; cursor: help; user-select: none; }
.pf-mp-help:hover, .pf-mp-help:focus { color: #2a6b84; outline: none; }
.pf-mp-help:focus-visible { outline: 2px solid #2a6b84; outline-offset: 2px; border-radius: 3px; }
.pf-mp-help::after { content: attr(data-tip); position: absolute; left: -10px; top: calc(100% + 6px); z-index: 30; width: 250px; box-sizing: border-box;
  padding: 8px 10px; border-radius: 8px; background: #101828; color: #fff; font: 400 12.5px/1.45 Arial, Helvetica, sans-serif; text-align: left;
  white-space: normal; box-shadow: 0 6px 16px rgba(16, 24, 40, .2); opacity: 0; visibility: hidden; pointer-events: none; transition: opacity .12s; }
.pf-mp-help:hover::after, .pf-mp-help:focus::after { opacity: 1; visibility: visible; }
/* `.pf-mp-set-f span` (display:block, margin-bottom) also matches the "?": keep it on the label's line */
.pf-mp-set-f .pf-mp-k .pf-mp-help { display: inline-block; margin: 0; font-size: 13px; color: #344054; }
.pf-mp-set-f .pf-mp-k .pf-mp-help:hover, .pf-mp-set-f .pf-mp-k .pf-mp-help:focus { color: #2a6b84; }
/* note: website-generator.css `.website_set_payment button` paints EVERY button in this panel the accent (!important) —
   Save and Remove come out teal there, and it is why the "?" must not be a <button> */
.pf-mp-claim { padding: 10px 12px; border: 1px solid #fedf89; background: #fffaeb; border-radius: 10px; margin: 8px 0; font-size: 14px; color: #344054; }
.pf-inv-mpclaim { padding: 0 12px 4px; }
.pf-mp-claim-acts { display: flex; flex-wrap: wrap; gap: 8px 12px; align-items: center; margin-top: 8px; }
.pf-mp-claim-acts label { display: inline-flex; align-items: center; gap: 6px; font-size: 13px; }
.pf-mp-amt { width: 90px; padding: 6px 8px; border: 1px solid #d0d5dd; border-radius: 8px; }
.pf-needs { width: 100%; border-collapse: collapse; }
.pf-needs td { padding: 8px 4px; border-top: 1px solid #eaecf0; vertical-align: middle; }
.pf-needs td.is-num { text-align: right; white-space: nowrap; }
.pf-ord-in.is-qty { flex: 0 0 64px; }
/* .pf-order-dialog zeroes .ui-dialog-content's padding (0,2,0); these panels ARE the content box. */
.pf-order-dialog .ui-dialog-content.pf-dun { padding: 12px 16px; }
/* The Invoices page's side panels (invoiceWidget.js _panel, PF.ui.panel cls pf-inv-panel): the
 * panel pads its own body, so the forms and lists inside it do not pad again. */
.pf-inv-panel .pf-dun { padding: 0; }
/* The full editor (drawInvoiceEditor): the template's parts sit in the panel's cards, so the
 * card title replaces each part's own heading, and the Business info / Choose a client /
 * Quote-Invoice strip sits in the panel's action bar without its old underline. */
.pf-inv-ed .pf-ui-panel-sec-b .pf-form-section { display: none; }
.pf-inv-ed .pf-inv-ed-bar { flex: 1 1 auto; min-width: 0; }
.pf-invoice.pf-inv-ed .pf-inv-ed-bar .editor { padding: 0; border-bottom: 0; gap: 14px; }
.pf-inv-ed .pf-ui-panel-sec-b .pf-inv-summary { max-width: 440px; }
/* The owner's view of one invoice (invoiceWidget.js _invShow): the document on Invoice, the money
 * on Payments, the feed on History; Record a payment / Refund and the activity's tools in the bar. */
.pf-inv-view .pf-ui-panel-bar { gap: 6px 14px; }
.pf-inv-view .pf-inv-money { display: inline-flex; gap: 6px; }
.pf-inv-view .pf-inv-act-tools:empty { display: none; }
.pf-inv-view .pf-inv-pay-sum { font-weight: 600; color: #101828; margin: 0 0 10px; }
.pf-inv-view .pf-inv-mpclaim { padding: 0; }
.pf-inv-view .pf-inv-act-body { max-height: none; overflow: visible; padding: 0; }
.pf-inv-view .pf-inv-paylist { margin-top: 6px; }
/* --- New order / New invoice (quick_invoice.js) ---------------------------------------
 * Modelled on the Kitchen board's New order form (kitchenBoardPages.js .pfk-order): system
 * font, slate ink, a small muted label over each field, 8px inputs, pill toggles that fill
 * with the accent, and ONE 12px step between every block.
 * jQuery UI writes an INLINE display:block on the content when it opens, which is why the old
 * `.pf-qi { display:flex }` never applied: the flex has to be !important. Other rules that
 * must beat the theme say .ui-dialog. */
/* The tokens, for the dialog and for the side panel it now opens in (PF.ui.panel, quick_invoice.js). */
.ui-dialog.pf-qi-dialog, .pf-ui-panel.pf-qi-panel {
    --qi-ink: #0f172a; --qi-ink-2: #334155; --qi-muted: #64748b; --qi-faint: #94a3b8; --qi-line: #e6e9ee;
    --qi-accent: var(--pf-accent, #2a6b84);
}
.ui-dialog.pf-qi-dialog {
    padding: 0; border: 0; border-radius: 14px; overflow: hidden; box-shadow: 0 18px 50px rgba(15, 23, 42, .28);
    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
}
.ui-dialog.pf-qi-dialog .ui-dialog-titlebar { padding: 18px 20px 0; border: 0; background: #fff; }
.ui-dialog.pf-qi-dialog .ui-dialog-titlebar .ui-dialog-title {
    height: auto; margin: 0; font-size: 17px; line-height: 1.3; font-weight: 600; color: var(--qi-ink);
}
.ui-dialog.pf-qi-dialog .ui-dialog-content.pf-qi {
    display: flex !important; flex-direction: column; gap: 12px; padding: 4px 20px 16px;
    font-size: 14px; line-height: 1.45; color: var(--qi-ink-2);
}
.pf-qi *, .pf-qi *::before, .pf-qi *::after { box-sizing: border-box; }
.pf-qi [hidden] { display: none !important; }
.pf-qi-sub { margin: 0; font-size: 12px; line-height: 1.5; color: var(--qi-muted); }
.pf-qi-f { display: flex; flex-direction: column; gap: 4px; margin: 0; }
.pf-qi-lbl { display: block; font-size: 12px; color: var(--qi-muted); font-weight: 400; }
.pf-qi .pf-ord-in {
    width: 100%; min-width: 0; flex: none; margin: 0; padding: 7px 9px;
    border: 1px solid var(--qi-line); border-radius: 8px; background: #fff;
    font: inherit; font-size: 13px; color: var(--qi-ink); box-shadow: none;
}
.pf-qi .pf-ord-in:focus { outline: none; border-color: var(--qi-accent); box-shadow: 0 0 0 3px rgba(42, 107, 132, .15); }
.pf-qi .pf-ord-in::placeholder { color: var(--qi-faint); }
.pf-qi textarea.pf-ord-in { min-height: 58px; resize: vertical; }
.pf-qi-who { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 12px; }
.pf-qi-who label { display: flex; flex-direction: column; gap: 4px; margin: 0; }
.pf-qi-matches { display: flex; flex-direction: column; gap: 4px; }
.pf-qi-matches:empty { display: none; }
.pf-qi-match {
    padding: 7px 10px; border: 1px solid var(--qi-line); border-radius: 8px; background: #fff;
    font: inherit; font-size: 13px; color: var(--qi-ink); text-align: left; cursor: pointer;
}
.pf-qi-match:hover { border-color: var(--qi-faint); }
.pf-qi-match em { font-style: normal; color: var(--qi-muted); font-size: 12px; }
/* Item | Qty | Price | x -- the header row and every line share one grid. */
.pf-qi-lhead, .pf-qi-line { display: grid; grid-template-columns: minmax(0, 1fr) 64px 110px 24px; gap: 12px; align-items: start; }
.pf-qi-lines { display: flex; flex-direction: column; gap: 8px; }
.pf-qi-name { position: relative; display: flex; flex-direction: column; min-width: 0; }
.pf-qi-cat { display: flex; flex-direction: column; }
.pf-qi-cat button {
    padding: 6px 9px; border: 1px solid var(--qi-line); border-top: 0; background: #fff;
    font: inherit; font-size: 12px; color: var(--qi-ink); text-align: left; cursor: pointer;
}
.pf-qi-cat button em { float: right; font-style: normal; color: var(--qi-muted); }
.pf-qi-del { width: 24px; height: 33px; padding: 0; border: 0; background: none; font-size: 18px; line-height: 1; color: var(--qi-faint); cursor: pointer; }
.pf-qi-del:hover { color: #b91c1c; }
.pf-qi .pf-ord-link { align-self: flex-start; margin-top: 4px; padding: 0; border: 0; background: none; font: inherit; font-size: 13px; color: var(--qi-accent); cursor: pointer; }
.pf-qi > .pf-ord-link { margin-top: 0; }
.pf-qi-total { display: flex; flex-wrap: wrap; justify-content: flex-end; align-items: baseline; gap: 0 8px;
    padding-top: 12px; border-top: 1px solid var(--qi-line); }
.pf-qi-total .pf-qi-lbl { display: inline; }
.pf-qi-total b { font-size: 16px; font-weight: 700; color: var(--qi-ink); }
.pf-qi-total em { flex-basis: 100%; text-align: right; font-style: normal; font-size: 12px; color: var(--qi-muted); }
/* Pill toggles (Kitchen's "Ready by" buttons): Due picks one, Send turns each on or off. */
.pf-qi-pills { display: flex; flex-wrap: wrap; gap: 8px; }
.pf-qi-pills button {
    margin: 0; padding: 6px 14px; border: 1px solid var(--qi-line); border-radius: 999px; background: #fff;
    font: inherit; font-size: 13px; color: var(--qi-ink-2); cursor: pointer; box-shadow: none;
}
.pf-qi-pills button:hover { border-color: var(--qi-faint); }
.pf-qi-pills button[aria-pressed="true"] { background: var(--qi-accent); border-color: var(--qi-accent); color: #fff; font-weight: 600; }
.pf-qi-sw[aria-pressed="true"]::before { content: "\2713\00a0"; }
.pf-qi-hint, .pf-qi .pf-dun-h { font-size: 12px; line-height: 1.5; color: var(--qi-muted); }
.pf-qi-chk { display: inline-flex; align-self: flex-start; align-items: center; gap: 8px; font-size: 13px; color: var(--qi-ink-2); cursor: pointer; }
.pf-qi-chk input { margin: 0; }
.pf-qi-dep { display: flex; flex-wrap: wrap; align-items: center; gap: 12px; }
.pf-qi-dep .pf-ord-in.is-money { width: 110px; }
.pf-qi-dep .pf-ord-in.is-qty { width: auto; }
.pf-qi-dep .pf-dun-h { flex-basis: 100%; }
.pf-qi .pf-ord-msg:empty { display: none; }
/* Footer: the Kitchen form's bar -- a rule above, 8px buttons. */
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane { margin: 0; padding: 12px 20px; border-top: 1px solid var(--qi-line); background: #fff; }
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane .ui-dialog-buttonset { display: flex; gap: 8px; float: right; }
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane button {
    margin: 0; padding: 7px 15px; border: 1px solid var(--qi-line); border-radius: 8px;
    background: #fff; color: var(--qi-ink-2); font-family: inherit; font-size: 14px; box-shadow: none; text-shadow: none;
}
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane button .ui-button-text { padding: 0; }
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane button.save { background: var(--qi-accent); border-color: var(--qi-accent); color: #fff; font-weight: 600; }
.ui-dialog.pf-qi-dialog .ui-dialog-buttonpane button[disabled] { opacity: .6; cursor: default; }
@media (max-width: 560px) {
    .pf-qi-who { grid-template-columns: minmax(0, 1fr); }
    .pf-qi-lhead, .pf-qi-line { grid-template-columns: minmax(0, 1fr) 56px 90px 24px; gap: 8px; }
}

/* Invoices Phase 3 */
.pf-inv-aging { display: flex; flex-direction: column; gap: 6px; }
.pf-inv-aging[hidden] { display: none; }
.pf-inv-aging-row { display: grid; grid-template-columns: repeat(auto-fit, minmax(130px, 1fr)); gap: 8px; align-items: stretch; }
.pf-inv-aging-cur { align-self: center; font-weight: 600; color: #475467; }
.pf-inv-bucket {
    position: relative; display: flex; flex-direction: column; align-items: flex-start; gap: 1px;
    padding: 8px 10px 12px; border: 1px solid #e4e7ec; border-radius: 9px; background: #fff;
    font: inherit; text-align: left; cursor: pointer; overflow: hidden;
}
.pf-inv-bucket span { font-size: 12px; color: #667085; }
.pf-inv-bucket b { font-size: 15px; color: #101828; }
.pf-inv-bucket em { font-style: normal; font-size: 11px; color: #667085; }
.pf-inv-bucket i { position: absolute; left: 0; bottom: 0; height: 4px; background: #98a2b3; }
.pf-inv-bucket.is-late_1_30 i { background: #f2c14e; }
.pf-inv-bucket.is-late_31_60 i { background: #f08c3a; }
.pf-inv-bucket.is-late_61_90 i, .pf-inv-bucket.is-late_90 i { background: #d92d20; }
.pf-inv-bucket.is-late_90 b { color: #b42318; }
.pf-inv-bucket[aria-pressed="true"] { border-color: var(--pf-accent, #2a6b84); box-shadow: 0 0 0 1px var(--pf-accent, #2a6b84); }
.pf-inv-bucket[disabled] { cursor: default; opacity: 0.6; }
.pf-inv-filter { font-size: 13px; color: #344054; }
.pf-inv-filter[hidden] { display: none; }
.pf-ob-tool[aria-pressed="true"] { border-color: var(--pf-accent, #2a6b84); background: var(--pf-accent-fill, #d9eaf3); color: var(--pf-accent-dark, #1f5265); }
.pf-rec-act { white-space: nowrap; }
.pf-rec-act .pf-ord-link { margin-left: 10px; }
.pf-dun input[type="radio"] + input, .pf-dun label .pf-ord-in { flex: none; }

/* --- Collapsible sections in a dialog (pfSections, js/pf_dialogs.js) --------------------
 * New order / New invoice and the order detail dialog. A section is a card whose header is a
 * button; closed, it says in one muted line what it holds. Sub-sections carry a small
 * uppercase label, the Kitchen board's column-head style. */
.pf-sec { border: 1px solid #e6e9ee; border-radius: 10px; background: #fff; }
.pf-sec-h {
    display: flex; align-items: center; gap: 10px; width: 100%; margin: 0; padding: 11px 14px;
    border: 0; border-radius: 10px; background: none; box-shadow: none;
    font: inherit; font-size: 14px; text-align: left; color: #0f172a; cursor: pointer;
}
.pf-sec-h:hover { background: #f8fafc; }
.pf-sec-h:focus-visible { outline: 2px solid var(--pf-accent, #2a6b84); outline-offset: -2px; }
.pf-sec.is-open > .pf-sec-h { border-radius: 10px 10px 0 0; }
.pf-sec-t { flex: 0 0 auto; font-weight: 600; }
/* The dialog theme colours every button grey at (0,2,1); a section title is a heading. */
.ui-dialog .pf-sec > .pf-sec-h, .ui-dialog .pf-sec > .pf-sec-h .pf-sec-t { color: #0f172a; font-family: inherit; }
.pf-sec-sum { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; font-size: 12px; color: #64748b; }
.pf-sec.is-open > .pf-sec-h .pf-sec-sum { visibility: hidden; }
.pf-sec-sum { font-size: 13px; color: #475467; }
.pf-sec-sum.is-empty { color: #94a3b8; }
.pf-sec-chev { flex: 0 0 auto; color: #94a3b8; transition: transform .15s; }
.pf-sec.is-open > .pf-sec-h .pf-sec-chev { transform: rotate(180deg); }
.pf-sec-b { display: flex; flex-direction: column; gap: 12px; padding: 2px 14px 14px; }
.pf-sec-b[hidden] { display: none; }
.pf-sub { display: flex; flex-direction: column; gap: 6px; }
.pf-sub-t { font-size: 11px; font-weight: 600; letter-spacing: .05em; text-transform: uppercase; color: #64748b; }
/* The expand / collapse-all icon, left of the dialog's close button. */
.ui-dialog .ui-dialog-titlebar .pf-sec-all {
    position: absolute; top: 50%; right: 36px; transform: translateY(-50%);
    display: inline-flex; align-items: center; justify-content: center; width: 28px; height: 28px;
    margin: 0; padding: 0; border: 1px solid transparent; border-radius: 7px; background: none; box-shadow: none;
    color: #475467; cursor: pointer;
}
.ui-dialog .ui-dialog-titlebar .pf-sec-all:hover { border-color: #e6e9ee; background: #f8fafc; color: #0f172a; }
/* New order: the sections carry the rhythm, so the panel's own gap stays 12px between cards. */
.pf-qi .pf-qi-total { border-top: 0; padding-top: 0; }
/* Order detail dialog in sections: the cards carry the separation now, so the old section
 * rules (a padded band with a rule above) step aside inside them. */
.pf-ord-dlg, .pf-ord-card-slot { display: flex; flex-direction: column; gap: 10px; }
.pf-ord-card-slot:empty { display: none; }
.pf-ord-dlg .pf-ord-head { padding: 10px 0 2px; border-bottom: 0; }
.pf-sec .pf-ord-actions { padding: 0; border-bottom: 0; }
.pf-sec .pf-ord-totals { border-top: 0; }
.pf-sec .pf-ord-act-t { font-size: 11px; font-weight: 600; letter-spacing: .05em; text-transform: uppercase; color: #64748b; }
.pf-ord-cust-slot:empty { display: none; }
.pf-order-dialog .ui-dialog-titlebar { min-height: 28px; }
/* New order: the catalogue as tap-to-add chips (name + price). Capped at ~3 rows; more scroll. */
.pf-qi-pickw[hidden] { display: none; }
.pf-qi-pick { display: flex; flex-wrap: wrap; gap: 8px; max-height: 132px; overflow-y: auto; padding: 1px; }
.pf-qi-pick button {
    display: inline-flex; align-items: baseline; gap: 6px; max-width: 100%; margin: 0; padding: 6px 12px;
    border: 1px solid #e6e9ee; border-radius: 999px; background: #fff; box-shadow: none;
    font: inherit; font-size: 13px; color: #0f172a; cursor: pointer;
}
.pf-qi-pick button span { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.pf-qi-pick button em { font-style: normal; font-size: 12px; color: #64748b; }
.pf-qi-pick button:hover { border-color: var(--pf-accent, #2a6b84); background: #f0f7fa; }
