.spinner
{
    margin: auto auto;
    width: 50px;
    height: 40px;
    text-align: center;
    font-size: 10px;
}

.spinner > div
{
    background-color: #00BBBB;
    height: 100%;
    width: 6px;
    display: inline-block;
    -webkit-animation: sk-stretchdelay 1.2s infinite ease-in-out;
    animation: sk-stretchdelay 1.2s infinite ease-in-out;
}

.spinner .rect2
{
    -webkit-animation-delay: -1.1s;
    animation-delay: -1.1s;
}

.spinner .rect3
{
    -webkit-animation-delay: -1.0s;
    animation-delay: -1.0s;
}

.spinner .rect4
{
    -webkit-animation-delay: -0.9s;
    animation-delay: -0.9s;
}

.spinner .rect5
{
    -webkit-animation-delay: -0.8s;
    animation-delay: -0.8s;
}

@-webkit-keyframes sk-stretchdelay
{
    0%, 40%, 100%
    {
        -webkit-transform: scaleY(0.4);
    }

    20%
    {
        -webkit-transform: scaleY(1.0);
    }
}

@keyframes sk-stretchdelay
{
    0%, 40%, 100%
    {
        transform: scaleY(0.4);
        -webkit-transform: scaleY(0.4);
    }

    20%
    {
        transform: scaleY(1.0);
        -webkit-transform: scaleY(1.0);
    }
}
/* Boot progress next to the loading spinner in every portal layout. Blazor sets
   --blazor-load-percentage-text while it downloads the app. The server-prerendered spinner has no
   language yet, so it shows the bare percentage, starting at 0% before the first update; once the
   app is interactive the text is "Loading" plus the percentage (no fallback: the mobile app never
   sets the variable and keeps the plain "Loading"). */
.loading-progress-span::after
{
    content: var(--blazor-load-percentage-text);
}

.loading-progress-span-initial::after
{
    content: var(--blazor-load-percentage-text, "0%");
}