Title: Full width container behaviour – Block vs. Document setting
Last modified: May 25, 2020

---

# Full width container behaviour – Block vs. Document setting

 *  Resolved [jmslbam](https://wordpress.org/support/users/jmslbam/)
 * (@jmslbam)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/full-width-container-behaviour-block-vs-document-setting/)
 * 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/](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](https://wordpress.org/support/users/edge22/)
 * (@edge22)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/full-width-container-behaviour-block-vs-document-setting/#post-12890452)
 * 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](https://wordpress.org/support/users/jmslbam/)
 * (@jmslbam)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/full-width-container-behaviour-block-vs-document-setting/#post-12914005)
 * 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](https://wordpress.org/support/users/edge22/)
 * (@edge22)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/full-width-container-behaviour-block-vs-document-setting/#post-12916388)
 * 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.

 * ![](https://ps.w.org/generateblocks/assets/icon.svg?rev=3239461)
 * [GenerateBlocks](https://wordpress.org/plugins/generateblocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/generateblocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/generateblocks/)
 * [Active Topics](https://wordpress.org/support/plugin/generateblocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/generateblocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/generateblocks/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Tom](https://wordpress.org/support/users/edge22/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/full-width-container-behaviour-block-vs-document-setting/#post-12916388)
 * Status: resolved