Opened 16 months ago
#58649 new defect (bug)
Legacy Widget does not save additional css classes
Reported by: | DeveloperWil | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 6.2.2 |
Component: | Widgets | Keywords: | |
Focuses: | administration | Cc: |
Description
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
Note: See
TracTickets for help on using
tickets.