[wp-trac] [WordPress Trac] #60877: Twenty Twenty-Four: Many block styles affect all blocks

[WordPress Trac]

#60877: Twenty Twenty-Four: Many block styles affect all blocks
--------------------------------------------+------------------------------
 Reporter:  wildworks                       |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  new
 Priority:  normal                          |   Milestone:  Awaiting Review
Component:  Bundled Theme                   |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  needs-testing-info needs-patch  |     Focuses:  ui, css
--------------------------------------------+------------------------------

Comment (by wildworks):

 Sorry for the late reply.

 If including the block class name in the CSS selector is a breaking
 change, should we close this ticket as "wontfix"? It may not be a problem
 if there is a way to remove unintended CSS classes without the user having
 to code them.

 However, when defining block styles in a new default theme that will be
 added in the future, it is better to decide whether to include the block
 class name in the CSS selector based on the expected specifications.

 Related to this ticket, it might be a good idea to discuss whether or not
 to copy additional CSS classes when copying blocks in the first place. See
 https://github.com/WordPress/gutenberg/issues/60352#issuecomment-2106100503

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