One of the saddest UX failures of Drupal (and now Backdrop) is when someone updates field display settings four or five times with no effect. Usually this is because they click the "Update" button thinking their settings will update, but they don't. Not unless they also hit "Save". And the "Save" button is usually below the fold, so the poor unsuspecting user may not even know there is a save button.

Secret save

To solve this problem, we should make the update button actually save, too.
Related issue: https://github.com/backdrop/backdrop-issues/issues/573
Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026
If there's some time left in the dev meeting - although it might rather be a topic for the PMC: We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
Weekly Meetings July 23rd 2026
The need for a clear AI policy is growing. Please can this be a priority.
Weekly Meetings July 23rd 2026