[wp-trac] [WordPress Trac] #53801: Block-based Widgets Screen does action wp_footer after each Widget

WordPress Trac noreply at wordpress.org
Thu Sep 2 19:31:46 UTC 2021


#53801: Block-based Widgets Screen does action wp_footer after each Widget
-------------------------------------+---------------------
 Reporter:  MadtownLems              |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  5.8.2
Component:  Widgets                  |     Version:  5.8
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------

Comment (by costdev):

 @zieladam
 > I am not sure how I feel about the proliferation of #page >
 :not(#content) rules – it seems a bit excessive.

 I agree, however both `#page` and `#content` could have content added to
 them by scripts, so this is part of strictly focusing on "Hide any extra
 content a) rendered by PHP and b) added in the runtime by javascript".

 > Either way, I would say now it's all about finding out whether or not we
 can find a popular plugin or a script that would unintentionally break it.
 My guess is "no", but I'm happy to be wrong here.

 Absolutely. For anyone reading this, please apply
 [https://core.trac.wordpress.org/attachment/ticket/53801/53801_css02.diff
 this patch] and let us know if you have any unexpected additional content
 in your legacy widget previews.

 @seedsca

 > It seems to me that the best way to deal with this is not enabling this
 feature when there are legacy widgets active and show a notice of how much
 better the widget editing workflow would be if the site was using the
 Block-based Widgets instead. Slow, but safe.

 Now that legacy widget previews have already been released, I think
 removing them is no longer an option. However, an unintrusive or one-time
 notice may be worth adding at some point. I'm not sure that that's within
 the scope of this ticket, but if you do open a new ticket, I'd be happy to
 contribute to that discussion.

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


More information about the wp-trac mailing list