Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1077516

    Hi,
    unless I put a masonry gallery into a grid row the top and left padding (defined in masonry_entries.css – line 155 ff)

    
    /*gap variations between elements: no, 1px and large*/
    .av-large-gap.av-masonry{ padding:15px 0 0 15px; }

    is overridden by

    
    masonry_entries.css (line 435ff)
    /*masonry within columns/sections */
    #top .container .av-masonry{background: transparent;}
    #top .container .av-masonry.av-large-gap {
      padding: 0;
      width: 102%;
      width: calc(100% + 15px);
    }

    Is it ALWAYS best practice to put everything in a grid row or why would the thing work differently if I “only” use columns

    #1078126

    Hey HaraldP,

    Where can we see the problem in question?

    Best regards,
    Rikard

    #1078963

    Hello Rikard,

    Thanks for your reply.
    Here you can see the problem in action:

    For the probably same/related problem with Header Elements, see:

    What is best practice with basic page layout? Put everything into Grid Rows?
    Cant find anything about “best practice” in the Enfold documentation – maybe consider adding a section containing any “musts”.

    Thx for your help.
    Harald

    #1080638

    Hi,

    Thanks for the update.

    Grid row is a full width element without an inner container, so it’s not constrained or limited by the “Maximum Container width” value unlike color sections or columns inside a generic section. Here’s the structure of the grid row compare to the default sections.

    Grid Row:

    
    <div class="av-layout-grid-container">
     // content here</div>
    

    Section:

    
    <div class="avia-section">
    <div class="container"> <-- the width of this container is limited and is based on the value set in the General Layout > Dimensions > Maximum Container width option
       // content here</div>
    </div>
    

    Best regards,
    Ismael

    #1080753

    Thanks for the insight, Ismael.
    So, this affects (top, left) padding on the masonry gallery, because …
    … grid-container-class has a 0 padding defined, which overrides the gallery´s padding?
    No, wait: [#top .container .av-masonry.av-large-gap] overrides [.av-large-gap.av-masonry] s padding´

    But why would the existence of a container affect the av-masonry-gap (top, left) ?
    Makes no sense to me. I would consider this a bug.
    Thx
    H

    • This reply was modified 5 years, 8 months ago by HaraldP.
    #1081451

    Hi,

    Thanks for the update.

    Yeah, I see your point. This looks like a bug. You can readd the padding back temporarily like this.

    #top .container .av-masonry.av-large-gap {
        padding: 15px 0 0 15px;
    }

    Best regards,
    Ismael

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.