[wp-trac] [WordPress Trac] #58649: Legacy Widget does not save additional css classes

WordPress Trac noreply at wordpress.org
Wed Jun 28 00:31:32 UTC 2023


#58649: Legacy Widget does not save additional css classes
----------------------------+-----------------------------
 Reporter:  DeveloperWil    |      Owner:  (none)
     Type:  defect (bug)    |     Status:  new
 Priority:  normal          |  Milestone:  Awaiting Review
Component:  Widgets         |    Version:  6.2.2
 Severity:  normal          |   Keywords:
  Focuses:  administration  |
----------------------------+-----------------------------
 Additional CSS Classes do not save on Legacy Widgets.

 * Install a new WordPress 6.2.2 site.
 * Activate a non-block theme that supports widgets. I used Twenty Twenty-
 One
 * Navigate to Appearance > Widgets
 * Select Footer area
 * Add a Navigation Menu (this creates a Legacy Widget) or add a Legacy
 Widget
 * Navigate to the Legacy Widget block options Advanced > Additional CSS
 Class(es)
 * Add any class name and update the widget area
 * Refresh admin screen
 * Navigate back to the Legacy Widget block options Advanced > Additional
 CSS Class(es)
 * The additional class name has not been saved.

 Also - if a legacy widget has any class names for earlier non-block-
 enabled widget areas, the class names are not pulled through to the Legacy
 Widget block options.

 If you edit a Legacy Widget, it will lose any additional class names
 previously applied (before the widget area was blockified).

 Loom recording example:
 https://www.loom.com/share/89afd2521bd44b25adc22642fd9be030

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


More information about the wp-trac mailing list