Yes, I am, but I’ve wanted to push & pull the positioning for the h1, h3 and button and then the h4 below, so the positions are different per screen size. (LG & MD, positioned right, SM & XSM, horizontally Centered)
Wonderful to have this explained, and further evidence (and with gratitude) for what I replied in our other dialogue Carousel Caption Area -- Class Control - #15 by DanielF regarding the creation of a Blocs Book that will explain all of these ‘under the hood’ (i.e. invisible) controlling factors to pre-packaged components. Knowing this would have saved me hours of trying to figure out why what I do (see) in the editor, with Custom Classes, doesn’t then get translated onto the rendered device screen.
Another excellent explanation…something that would be so welcomed in the Blocs Book I envision for folks like me.
Yes, this one I’ve noticed occurring, and so make sure to check each device size when I make custom changes on any one of them…which of course is a time consuming step.
another great entry for the Blocs Book…hint hint, maybe you will write one???
oh darn, I was doing just the opposite, because I thought the Margin was causing the havoc…again, something I’ve been trying to chase down on my own…so, this is good to know! Much gratitude, to our future author of the Blocs Book: Let’s get under the Hood, edition 1 by @hendon52 . 