/*
 * This is a manifest file that'll be compiled into application.css.
 *
 * With Propshaft, assets are served efficiently without preprocessing steps. You can still include
 * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard
 * cascading order, meaning styles declared later in the document or manifest will override earlier ones,
 * depending on specificity.
 *
 * Consider organizing styles into separate files for maintainability.
 */


.claim-a-listing-button{
    position: fixed;
    width: 200px;
    top: calc(50% - 0px);
    transform: rotate(270deg);
    left: -80px;
    background: oklch(54.6% 0.245 262.881);
    height: 40px;
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    z-index: 999;
    color: white;
    font-weight: 700;
}

.listing-shortcut-button{
    position: fixed;
    width: 155px;
    top: calc(50% - 100px);
    right: 0px;
    background: white;
    display: flex;
    gap: 4px;
    flex-direction: column;
    justify-content: center;
    z-index: 999;
    color: white;
    font-weight: 700;
    padding: 16px;
    box-shadow: rgba(100, 100, 111, 0.2) 0px 7px 29px 0px;
    border-radius: 10px 0px 0px 10px;
}
.listing-shortcut-button-unactive{
    padding: 10px;
    display: flex;
    gap: 8px;
}
.listing-shortcut-button-active{
    background: oklch(0.87 0.07 269.03);
    padding: 10px;
    border-radius: 6px;
}

.listing-shortcut-button-active svg{
    fill: #235afb
}
.listing-shortcut-button-active p{
    color: #235afb;
}