/**
 * Copyright © Magefan (support@magefan.com). All rights reserved.
 * See LICENSE.txt for license details (http://opensource.org/licenses/osl-3.0.php).
 *
 * Glory to Ukraine! Glory to the heroes!
 */
.post-content.post-custom {
    padding: 20px;
    border: 1px solid #ddd;
}

.post-list-wrapper .post-list {
    padding: 0;
}

.post-content .post-description .post-ftimg-hld img {
    width: auto;
}

.post-holder {
    background: none;
    padding: 0;
    margin-bottom: 40px;
    box-shadow: none !important;
    -webkit-box-shadow: none !important;
}

.post-content.post-custom .post-description .post-ftimg-hld {
    width: 270px;
    margin: 0;
    float: left;
}

.post-content.post-custom .post-description .post-info-blog {
    margin-left: 300px;
}

.post-content.post-custom .post-description .post-title-holder {
    display: table;
    width: 100%;
}

.post-content.post-custom .post-description .post-title {
    margin: 0 0 15px;
    padding: 0;
    font-size: 100%;
}

.post-content.post-custom .post-description .post-title a {
    font-size: 114.285%;
    font-weight: 600;
    color: #222;
}

.post-list .post-holder .post-header .addthis_toolbox {
    padding-top: 2px;
}

.post-content.post-custom .post-description .post-info-blog .dash {
    display: none;
}

.post-content.post-custom .post-description .post-info-blog .post-categories {
    display: none;
}

.post-content.post-custom .post-description .post-info-blog .post-text-hld {
    display: table;
    width: 100%;
    margin-bottom: 10px;
}

.post-content.post-custom .post-description .post-info-blog .post-read-more {
    display: table;
    float: none;
    padding: 9px 30px;
    color: #222;
    background-color: #f5f5f5;
    border-radius: 5px;
    -webkit-border-radius: 5px;
}

.post-holder .post-header .post-info .item {
    margin-right: 5px;
}

.post-holder .post-header .post-info .label {
    font-weight: 400;
}

.widget.block.blog-search .block-content {
    background: #f7f7f7;
    border: 1px solid #ddd !important;
    border-radius: 10px;
    -webkit-border-radius: 10px;
}

.widget.block.block-rss .block-title {
    background: none;
    padding: 0;
}

.widget.block.block-rss .block-title strong {
    text-transform: none;
}

.widget.blog-search .action.search {
    top: 0;
    padding: 0 !important;
    width: 35px;
    right: 0;
}

.widget.block-rss .rss-icon {
    padding-right: 7px;
    margin-top: 2px;
}

.sidebar .widget.blog-search {
    float: none;
}

.widget.block-recent-posts .block-content .item {
    padding: 5px 0;
}

.widget.block-list-posts .block-content .item .post-image {
    background: none;
    border: none;
    padding: 0;
}

.widget.block-list-posts .post-item-date {
    font-size: 90%;
}

.post-holder {
    border: none;
}

.post-content .post-description .post-ftimg-hld img {
    margin: 0 15px 10px 0;
    float: left;
}

.c-replyform {
    margin-left: 0 !important;
    margin-right: 0 !important;
}

.c-replyform.no-active textarea {
    height: 70px !important;
    border-radius: 4px;
    -webkit-border-radius: 4px;
}

.c-replyform textarea {
    height: 100px !important;
    border-radius: 4px 4px 0 0;
    -webkit-border-radius: 4px 4px 0 0;
}

.c-replyform button {
    padding: 6px 20px !important;
    margin-top: 0 !important;
}

.rtl-layout .post-list .post-header .post-title {
    float: right;
}

.rtl-layout .post-list .post-holder .post-header .addthis_toolbox {
    float: left;
}

@media (min-width: 768px) {
    .rtl-layout .post-content .post-description .post-ftimg-hld {
        float: right;
    }

    .rtl-layout .post-content.post-custom .post-description .post-info-blog {
        margin-right: 300px;
        margin-left: 0;
    }
}

@media (max-width: 767px) {
    .post-content.post-custom .post-description .post-ftimg-hld {
        width: 100%;
        float: none;
    }

    .post-content.post-custom .post-description .post-info-blog {
        margin-left: 0;
        margin-right: 0;
        float: none;
        padding-top: 15px;
    }

    .post-content .post-description .post-ftimg-hld img {
        width: 100%;
        float: none;
        margin: 0 0 10px 0;
    }
}
/* ---------------------------------------------------------------------------
 * BLOG PAGINATION — restore the pager the theme hides.
 *
 * The Sm/autostore theme generates css/config_default.css containing:
 *     .toolbar .pages                     { display: none; }
 *     .products.wrapper ~ .toolbar .pages { display: block; }
 * i.e. every pager is hidden and then re-shown ONLY for product grids. The blog's
 * toolbar is .toolbar-blog-posts following a post list, not .products.wrapper, so it
 * stays hidden: the markup, the Next control and ?page=2 all work, and none of it is
 * visible. That is why the blog appeared to have no way back to older posts.
 *
 * WHY HERE AND NOT IN config_default.css. That file is GENERATED at static-content
 * deploy and is not in git, so a fix applied to it survives exactly until the next
 * deploy — which is how this regressed: it was fixed on staging, and the cutover's
 * static deploy regenerated the file and wiped it. This file is theme source, tracked
 * in git, and is deployed on every build.
 *
 * Specificity is deliberately 0,3,0 (page class + two classes) so it wins over the
 * theme's 0,2,0 rule regardless of stylesheet order.
 * ------------------------------------------------------------------------- */
.blog-page .toolbar.toolbar-blog-posts .pages,
.blog-index-index .toolbar.toolbar-blog-posts .pages {
    display: block;
    float: none;
    text-align: center;
    margin: 20px 0 10px;
}

.blog-page .toolbar.toolbar-blog-posts .pages .pages-items,
.blog-index-index .toolbar.toolbar-blog-posts .pages .pages-items {
    display: inline-block;
}

/* ---------------------------------------------------------------------------
 * POST BODY TYPOGRAPHY — restore heading weight and spacing.
 *
 * css/yttheme.css loads after the blog stylesheets and flattens every heading
 * site-wide:
 *     h2, h3 { font-weight: normal; margin-top: 0; margin-bottom: 0; }
 * On a product page that is intended. Inside an article it removes the two
 * things that make long-form copy readable: headings stop being bold, so they
 * no longer separate sections, and their margins collapse to zero, so a heading
 * sits flush against the paragraph beneath it with no visual break.
 *
 * Nothing in the blog CSS competed with it — measured on the live page, the
 * winning rules for .post-description h2 came from styles-m, ytextend and
 * yttheme only, with computed font-weight 400 and margin 0px.
 *
 * Scoped to the article body so product and category pages keep the theme's
 * intended headings. Specificity 0,1,1 beats yttheme's bare 0,0,1 element
 * selector without needing !important.
 * ------------------------------------------------------------------------- */
.post-description h1,
.post-description h2,
.post-description h3,
.post-description h4,
.post-content h2,
.post-content h3 {
    font-weight: 700;
    margin-top: 1.9em;
    margin-bottom: 0.65em;
    line-height: 1.25;
}

/* NOTE: this theme sets a 10px root font-size, so 1rem = 10px, not 16px. An earlier
 * version of these rules used 1.55rem expecting ~25px and rendered 15.5px -- barely
 * larger than the 14px body copy. Measured on the live page, not assumed. The theme's
 * own h2 is 2.6rem (26px); these sit just under it so article headings read as headings
 * without competing with the page title. */
.post-description h2,
.post-content h2 { font-size: 2.4rem; }

.post-description h3,
.post-content h3 { font-size: 1.9rem; }

.post-description h4 { font-size: 1.6rem; }

/* First heading should not push the article away from the byline. */
.post-description > h1:first-child,
.post-description > h2:first-child,
.post-description > h3:first-child { margin-top: 0; }

.post-description p,
.post-content .post-description p {
    margin-bottom: 1.15em;
    line-height: 1.7;
}

.post-description ul,
.post-description ol {
    margin: 0 0 1.15em 1.4em;
    line-height: 1.7;
}

.post-description li { margin-bottom: 0.4em; }

/* ---------------------------------------------------------------------------
 * LINKS INSIDE POST CONTENT.
 *
 * Nothing styled them, so they inherited the body colour and were
 * indistinguishable from ordinary text — measured on the live page, links in
 * the article body computed to the same rgb(40,40,40) as the paragraphs around
 * them. A reader has no way to tell a link from a sentence.
 * ------------------------------------------------------------------------- */
.post-description a:not(.mini6-cta):not(.action),
.post-content .post-description a:not(.mini6-cta):not(.action) {
    color: #c8102e;
    text-decoration: underline;
    text-underline-offset: 2px;
}

.post-description a:not(.mini6-cta):not(.action):hover {
    color: #ee000b;
}

/* ---------------------------------------------------------------------------
 * PRODUCT CALL-TO-ACTION BUTTONS.
 *
 * Posts mark up shop links as <a class="mini6-cta">. The class carried no
 * styling, so two product CTAs at the end of the Mini6 article rendered as
 * plain grey text. Styled to match the theme's existing buttons (the blog's own
 * READ MORE), so a reader recognises them as something to click.
 * ------------------------------------------------------------------------- */
.post-description a.mini6-cta {
    display: inline-block;
    background: #ee000b;
    color: #fff;
    font-weight: 700;
    font-size: 1.3rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    text-decoration: none;
    padding: 11px 22px;
    border-radius: 3px;
    margin: 4px 8px 4px 0;
    transition: background .15s ease;
}

.post-description a.mini6-cta:hover,
.post-description a.mini6-cta:focus {
    background: #1c1c1c;
    color: #fff;
    text-decoration: none;
}

/* ---------------------------------------------------------------------------
 * ARTICLE POLISH.
 *
 * Three things were making long-form posts read as unfinished rather than as
 * editorial: inline images landed at their natural width (roughly 40% of the
 * column) flush left, so the page had a ragged left-weighted rhythm; lists lost
 * their markers and sat at paragraph spacing, so a list of fitment locations
 * looked like a run of one-line paragraphs; and 14px copy across a ~970px
 * column gives an uncomfortably long line.
 * ------------------------------------------------------------------------- */

/* Images fill the column and breathe, instead of floating small and left. */
.post-description img,
.post-content .post-description img {
    display: block;
    width: 100%;
    height: auto;
    margin: 1.8em 0;
    border-radius: 4px;
}

/* A caption-ish line immediately after an image should hug it, not drift. */
.post-description img + p,
.post-description p > img + br + em {
    margin-top: -0.6em;
}

/* Readable measure and size for body copy. */
.post-description,
.post-content .post-description {
    font-size: 1.55rem;
    line-height: 1.75;
    color: #2e2e2e;
}

/* Lists look like lists again. */
.post-description ul { list-style: disc outside; }
.post-description ol { list-style: decimal outside; }

.post-description ul,
.post-description ol {
    margin: 0 0 1.3em 1.6em;
    padding-left: 0.4em;
}

.post-description li {
    margin-bottom: 0.45em;
    line-height: 1.7;
    padding-left: 0.2em;
}

/* Lead-in emphasis lines ("U.S. Design Patent No. ... has been granted") read as
 * a standfirst rather than as a bold paragraph lost in the flow. */
.post-description > p:first-of-type > strong:only-child {
    display: block;
    font-size: 1.15em;
    line-height: 1.5;
    margin-bottom: .2em;
}

/* Keep the social-share row clear of the final CTA buttons. */
.post-description + .post-bottom,
.post-description > p:last-child { margin-bottom: 1.6em; }

/* ---------------------------------------------------------------------------
 * RELATED PRODUCTS / COMMENTS OVERLAP.
 *
 * The related-products block computed to 25px tall -- the height of its heading
 * alone -- while containing two ~300px product cards. Magento's product grid
 * floats its items, and neither .products.wrapper nor the .product-items list
 * contained those floats, so the block collapsed to nothing and the comments
 * block, laid out 50px below it, rendered ON TOP of the product cards.
 *
 * That is why the products were only clickable along their very top edge: the
 * comments block was covering everything beneath it, intercepting the clicks.
 *
 * flow-root makes each container establish a block formatting context and so
 * contain its floats, without the pseudo-element clearfix hack. The clear on
 * comments is belt and braces for the same failure elsewhere.
 * ------------------------------------------------------------------------- */
.mfblog-related-products-block,
.mfblog-related-products-block .block-content,
.mfblog-related-products-block .products.wrapper,
.mfblog-related-products-block .products-grid .product-items {
    display: flow-root;
}

.mfblog-related-products-block {
    margin: 2.5em 0 3em;
    clear: both;
}

/* The grid was also 999px inside a 969px parent — negative gutters escaping. */
.mfblog-related-products-block .products.wrapper {
    width: 100%;
    overflow: visible;
}

.post-view .block.comments,
.post-view #comments {
    clear: both;
    margin-top: 2em;
}
