Widgets generated by wp_register_sidebar_widget can not be add via customizer

[bastho]

Single use widgets, generated by wp_register_sidebar_widget and managed by wp_register_widget_control always return an "Invalid value" error in Customizer. They also block saving in Customizer.

We still can add them via appearance/widgets.php and go back to customizer.

Example to reproduce:

<?php
add_action('widgets_init', 'proof_of_concept_register_widget');
function proof_of_concept_register_widget(){
    wp_register_sidebar_widget(
        'poc_widget',
        'POC Widget',
        'poc_widget_display',
        array(
        'description' => 'POC for Customize bug'
        )
    );
    wp_register_widget_control('poc_widget', 'poc_widget', 'poc_widget_control');
}
function poc_widget_display(){
    echo '<p>POC for Customize bug</p>';
}
function poc_widget_control(){
    echo '<p>You should see a red notice "Invalid value" just above</p>';
}

[celloexpressions]

There is some logic in the old customize widgets class to address "single" (as opposed to "multi") widgets. However, it sounds like that may have broken at some point.

Now that widgets are replaced with blocks in 5.8, we need to confirm that "single" widgets "still" work. If they do, then this can likely be closed as fixed in 5.8. If they don't but we can confirm they were broken on 5.7 also, then this can maybe move to Future Release.

Given that the block inserter replaces the add-widgets panel in the customizer, this would probably need to be fixed with 5.8 as the widgets screen would also be broken now. Another option would be to formally deprecate "single" widgets.

[hellofromTonya]

Today is 5.8 Beta 1. Investigation is ongoing. Punting to 5.9.

[hellofromTonya]

5.9 Beta 1 is in < 19 hours. With no movement on this ticket, moving to 6.0 for further investigation.

[costdev]

Per the discussion in the bug scrub, I'm adding reporter-feedback to see if this is still an issue after the transition to Block Widgets.

[costdev]

This ticket was discussed in the bug scrub. As there has been no progress in quite some time, I'm moving this ticket to Future Release.