This is basically the equivalent of https://www.drupal.org/project/drupal/issues/3163226 (as well as a sibling issue to #5741) which was introduced in D 9.1.x (Change record: Core settings keys can be deprecated)
If the
settings.phpfile for a site (or any file it includes) contains the legacy setting name, the deprecation warning will be generated. If code callsSettings::get('new_setting')but'new_setting'is not yet defined, the value of'old_setting'will be returned.If any code calls
Settings::get()with the legacy name, the deprecation warning will also be generated. If the replacement setting is already defined, the value returned bySettings::get('old_setting')will be the value ofnew_setting.
This would help us with issues similar to #4451 as well, and possibly allow us to deprecate things in the Backdrop 1.x release cycle instead of having to wait for 2.x.
Recent comments
In case anybody comes back to this, I think I found the problem. The dropdowns disappear only on pages that do not have any images in the image gallery field. That's because mosaic_grid's JS was...
Vanishing dropdown in primary navigation
Some themes have a dedicated spot in the settings that you can add a few bits of custom CSS for the element you want or you could use CSS Injector I'm not sure which progress bar you mean...
How to change the width of the progress bar
I have just checked on Windows 11 and get no warnings on download. I also scanned the zip with Windows Defender and Malwarebytes and it was all clean.
Virus warning on 1.29.3 download