[wp-trac] [WordPress Trac] #61826: Inline Padding Issue with Full-Width (alignfull) Group in WordPress 6.6

WordPress Trac noreply at wordpress.org
Mon Aug 5 20:31:52 UTC 2024


#61826: Inline Padding Issue with Full-Width (alignfull) Group in WordPress 6.6
--------------------------+-----------------------------
 Reporter:  tremidkhar    |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The inline padding for full-width (alignfull) groups is not being applied
 as expected. This behavior differs from previous versions, specifically
 WordPress 6.5.5, where the padding was correctly applied.

 == Steps to Reproduce:

 Create or edit the header.html template.
 Add a full-width (alignfull) group with inline padding.
 Save the changes and view the header on the frontend.

 == Expected Behavior:

 In WordPress 6.5.5, the header displays with the root inline-padding for
 spacing.

 == Observed Behavior:

 In WordPress 6.6, the inline padding is not applied, and the header
 appears without any spacing.

 == Environment:

 WordPress Version: 6.6
 Theme: Twenty Twenty Four (with changes only to the header.html template)


 Below is a sample code snippet for the header.html template used for
 testing:

 {{{
 <!-- wp:group
 {"align":"wide","style":{"spacing":{"padding":{"top":"var:preset|spacing|30","bottom":"var:preset|spacing|30"}}},"layout":{"type":"constrained"}}
 -->
 <div class="wp-block-group alignwide" style="padding-top:var(--wp--preset
 --spacing--30);padding-bottom:var(--wp--preset--spacing--30)"><!--
 wp:group {"align":"full","layout":{"type":"default"}} -->
 <div class="wp-block-group alignfull"><!-- wp:group
 {"layout":{"type":"flex","flexWrap":"wrap","justifyContent":"space-
 between"}} -->
 <div class="wp-block-group"><!-- wp:group
 {"style":{"spacing":{"blockGap":"var:preset|spacing|20"},"layout":{"selfStretch":"fit","flexSize":null}},"layout":{"type":"flex"}}
 -->
 <div class="wp-block-group"><!-- wp:site-logo
 {"width":60,"shouldSyncIcon":true} /-->

 <!-- wp:group {"style":{"spacing":{"blockGap":"0px"}}} -->
 <div class="wp-block-group"><!-- wp:site-title {"level":0} /--></div>
 <!-- /wp:group --></div>
 <!-- /wp:group -->

 <!-- wp:group
 {"layout":{"type":"flex","flexWrap":"wrap","justifyContent":"left"}} -->
 <div class="wp-block-group"><!-- wp:navigation
 {"ref":5,"style":{"spacing":{"margin":{"top":"0"},"blockGap":"var:preset|spacing|20"},"layout":{"selfStretch":"fit","flexSize":null}},"layout":{"type":"flex","justifyContent":"right","orientation":"horizontal"}}
 /--></div>
 <!-- /wp:group --></div>
 <!-- /wp:group --></div>
 <!-- /wp:group --></div>
 <!-- /wp:group -->
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61826>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list