Mobile (breakpoints) padding FEATURE REQUEST

Beta
#1

Ok, i’ll try to explain what i mean.

  1. Global Container is off. So there is NO margin at all (old “Marginless columns”)
  2. Switching to any small breakpoint. So the column will “stick” to left and right corners cause of width 100% and margin 0 auto.

I want to have no padding on desktop, and have it on mobile. It would be a great thing if i could control column padding at any breakpoint individually. I can do it with @media css, but it takes a lot of time, as you know.

Here is a video. This is realy important thing and it already has long been used in all of content builders such as divi or visual composer.

2 Likes
#2

When the Global Container on the Row is set to off, it removes these classes from it: x-container max width.

I think it should also add a specific class to such Row, so we can target this specific behavior with a global Media Query.

Something like this:

@media screen and (max-width: 767px) {
    .marginless-columns.x-row {
padding-left:2em!important;
padding-right:2em!important;
}
}

In the meantime, we can always add our own class in through the Customize option. :slight_smile:

#3

Hi @Georgich,

Thanks for sharing the video! I see what you mean. We are going to have a way to override styling controls (Margin, Padding, Borders, etc.) per breakpoint (like other builders). If we don’t build it for the next cycle, we will be doing it for the Theme Options update to follow. This will add a whole new dimension of customization for the new Row because it will allow you to change things like gap sizes, flexbox reversing as well. I’m sorry it’s not in this release, but it’s definitely on our radar and a priority.

1 Like
#4

From your guys Facebook posts I had expected this now. I am actually quite disappointed with this release so far.

My opinion is that one of the more important things at the moment is more granular controls at different break points. X/Pro are great for desktop layouts but not great for responsive layouts which is really the cornerstone of any website.

By more granular controls I mean basically anything that can be set in an element should have the option for different settings at each break point ( Maybe you guys should buy Elementor and Oxygen for ideas).

While these granular controls are easily over ridden with custom css it is simply much faster to do in the builder. In the same one that one can code custom post types and custom fields it is simply faster in most instances to use CTP-UI / ACF to do these things.

Personally dragging windows around, being able to have floating settings boxes etc. are nice to have but should perhaps come down the line once the basics are complete.

Sorry I know this is a bit of a rant but I really love X/Pro which is the main reason I am still here while many others have jumped ship.

2 Likes
#5

@urchindesign Thanks for sharing. I believe the new Row and Columns are a move the the right direction, and as stated above the per-breakpoint customization is coming.

We know how important this feature is - and in the discovery we’ve done to date, we know it has the potential to add weeks of additional development time so we have to draw the line somewhere and break the work down into cycles. Getting this functionality to work on our Elements that have hundreds of data points is not as easy to do as some of the more UI related features. It opens up performance challenges, and may require rebuilding parts of our generated CSS system.

We’ve also got to be careful to spread out more of the “invasive” changes. In this cycle we refactored all our element code to make the Element API public, while also shaving off a fair amount of load time for the builders. The more systemic changes we introduce at once, the more risk there is for edge case regressions - these draw out release cycles and slow things down even more.

It’s certainly a priority to us, but we felt it wise to hold off a bit longer while we get some other pieces in place. Thanks for understanding. I do hope you find some value in this release in the meantime.

1 Like
#6

Yes! We really need this feature and I’m glad to hear it’s on your radar.
Now that v3 is released do you have any updates on when this feature might be released?

#7

Not yet, we’re still in the process of supporting this release with point releases and bug fixes. After that, we’ll be working on a smaller cycle primarily focused on the Grid element. Then we’ll circle back to this and determine if it will be in the layout builder cycle or later.