• Resolved jmslbam

    (@jmslbam)


    First, thanks! Just the lean plugin I needed. Ok here it goes. It’s more of an obersavation then a bug. Or maybe it is, it’s your call.

    Container block
    When I add a container block, there is an option available.

    Set Full Width Content

    This option tells the content container that contains all of the blocks on this page to be full width.

    This option on “block” level that triggers a “document” level behaviour suprises me.

    I suspected this behaviour to trigger only this block to go “full width”. Like described here https://www.billerickson.net/full-and-wide-alignment-in-gutenberg/.

    Only áfter reading the “fine prints” I understood this option. As I said, an document setting on a block level seems incorrect.

    In my case, I can already manage these settings through the “page builder container” of GeneratePress.

    Kind regards,

    Jaime Martinez

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tom

    (@edge22)

    Hi Jaime,

    Yes, this was my attempt to provide a shortcut to a GeneratePress option to make the content container full width. I noticed a lot of confusion about the block not being full width due to the actual content container, so my hope was this would help.

    In might be that it causes more confusion. If so, I’ll definitely remove it 🙂

    Thread Starter jmslbam

    (@jmslbam)

    Thank you for your anwser, I will simply hide it with some custom CSS in the back-end for now.

    Have a good weekend!

    Plugin Author Tom

    (@edge22)

    Sounds good! Thanks, you too 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Full width container behaviour – Block vs. Document setting’ is closed to new replies.