[wp-trac] [WordPress Trac] #61787: Twenty Twenty: Separator block (dots) does not render anymore

[WordPress Trac]

#61787: Twenty Twenty:  Separator block (dots) does not render anymore
----------------------------------------+---------------------
 Reporter:  mrfoxtalbot                 |       Owner:  (none)
     Type:  defect (bug)                |      Status:  new
 Priority:  normal                      |   Milestone:  6.7
Component:  Bundled Theme               |     Version:  6.6
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch has-testing-info  |     Focuses:  css
----------------------------------------+---------------------
Changes (by sabernhardt):

 * focuses:   => css
 * version:   => 6.6
 * milestone:  Awaiting Review => 6.7


Comment:

 Original report:
 https://github.com/Automattic/themes/issues/7978

 If this could be fixed in the editor, I would prefer that instead of
 changing the theme. GB61638 clearly
 [https://github.com/WordPress/gutenberg/blob/78a3e71ec3ff85944324c99b4128d6cb5cac5542/packages
 /block-library/src/separator/style.scss#L28 considered the Dots style],
 but I question whether any theme's JSON global styles should override
 rules such as the `auto` height or the pseudo-element `content` property.
 The same change also //increased// CSS specificity for the border styles
 after they were reduced in GB60740.

 I think @poena was suggesting that the theme might reduce the specificity
 for its `.entry-content hr` rules. I made [attachment:"61787.reduce-
 specificity.diff"] to consider that option.

 {{{
 // Specificity less than 0-1-0 to keep the dots
 :where(.entry-content) hr::before,
 :where(.entry-content) hr::after,

 // 0-1-0 is just enough to override `.wp-block-separator {border-top: 2px
 solid;}`
 .entry-content :where(hr:not(.is-style-dots))
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61787#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform