boolean_toggle_labeled

The class adds nothing but a template. All the interesting content is in the descriptor:

export const booleanToggleFieldLabeled = {
    ...booleanToggleField,
    component: BooleanToggleFieldLabeled,
    displayName: _t("ToggleLabeled"),
    supportedOptions: [
        {
            label: _t("Autosave"),
            name: "autosave",
            type: "boolean",
            default: true,
            help: _t("If checked, the record will be saved immediately when the field is modified."),
        },
    ],
};

It spreads the boolean toggle descriptor, swaps in a component whose only difference is a template that draws the label, and redeclares autosave with its default and help text.

The default matters: true. Flipping this toggle writes to the database straight away unless you explicitly turn that off.

Autosave on a toggle is a real decision, not a detail. It means a mis-click is committed, with no chance to discard. On a settings screen that is usually what you want, because nobody expects to save a settings page. On a record where the user might change their mind, it is a trap.

Odoo 20 removed the choice entirely. If your team relied on turning autosave off to make a toggle behave like a normal field edit, that protection is gone across every toggle in the system, not only on this widget.

In Odoo 19, with autosave left on by default:

<field name="is_published" widget="boolean_toggle_labeled"/>

Turning it off, so the change behaves like a normal edit:

<field name="is_published" widget="boolean_toggle_labeled"
       options="{'autosave': False}"/>

In Odoo 20 neither line works: the widget is gone, and so is the option.

This widget is the clearest single example of one of Odoo 20's larger changes.

We searched addons/web/static/src/views/fields/ on both branches for autosave. On 19.0 it appears in seven files, including boolean_toggle_field.js, priority_field.js, selection_field.js, state_selection_field.js, boolean_favorite_field.js and color_field.js. On 20.0 it appears in none. The option was not deprecated or renamed; it was deleted from the field library.

Four widgets that survive into Odoo 20 lost it as a declared option: boolean_toggle with 156 uses in Odoo 20 core, priority with 65, boolean_favorite with 17 and state_selection with 10. This widget lost it too, and was itself removed.

The consequence is quiet rather than loud. A view carrying options="{'autosave': False}" on a surviving widget installs without error in Odoo 20 and simply ignores the setting. Nothing warns. The toggle behaves however Odoo 20 decides it should, and the protection somebody added deliberately is gone.

If you have ever set autosave anywhere, search your views for it before an Odoo 20 upgrade. It is the sort of change that surfaces as a user complaint months later rather than as a failure on day one.

Removed. The registration is absent from the 20.0 branch.

More importantly, its one option went with the whole library. autosave no longer exists anywhere under addons/web/static/src/views/fields/ in Odoo 20, having appeared in seven files on the 19.0 branch. Four widgets that survive lost it as a declared option, so this is a system-wide behavioral change rather than a widget-specific one.

Views setting the option still install. They are silently ignored.