colors_reset_button

When a form lets users tune a group of settings, brand colors in the core case, someone will eventually want the factory values back. colors_reset_button is Odoo's smallest answer: a view widget that renders a refresh icon and, on click, writes a hardcoded dictionary of defaults into the record's fields.

The defaults are not baked into the widget. They arrive through the default_colors option in the view XML, one dictionary per placement, which is how the same widget resets the Livechat button colors in one group and the chat window colors in another, each to its own values.

The pattern this widget encodes, editable settings with a visible escape hatch, is what keeps configuration screens safe to explore. A marketer can experiment with Livechat branding knowing the factory look is one click away, so fewer support tickets start with we changed the colors and cannot get them back.

Because the widget is generic under the hood, it is also a ready-made piece for custom settings pages: any group of fields with sensible defaults, margins, thresholds, template choices, can get the same reset affordance by reusing this component or copying its twenty-line pattern into your own module.

Core's Livechat button colors

<widget name="colors_reset_button"
        options="{'default_colors': {'button_background_color': '#878787', 'button_text_color': '#FFFFFF'}}"/>

Placed right after the two color fields it resets, inside the same group.

Resetting any fields on a custom form

<widget name="colors_reset_button"
        options="{'default_colors': {'header_color': '#875A7B', 'accent_color': '#00A09D', 'footer_note': 'Powered by us'}}"/>

The keys are field names and the values are what they reset to; nothing restricts them to colors, only the option's name suggests it.

The whole component is small enough to audit in a minute, and two details are the ones that matter. The click handler is a single record.update(this.props.default_colors): an in-memory update that marks the form dirty and triggers onchange logic, with no save and no confirmation. Users can still discard. That makes it forgiving, but it also means the reset is not logged anywhere until the form is saved like any other edit.

The history of extractProps is a nice miniature of Odoo's widget API tightening. In 16 it forwarded the whole attrs.options object as props, so any stray key in the options dictionary would break props validation. Since 17 it plucks exactly options.default_colors, and the file has been byte-identical from 18 through the development branch, our diff of 19 against master came back empty, a stability streak few widgets manage.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. We read the widget's file on the public development branch at the time of writing; the branch is unstable and this page will be re-verified after release.

Zero changes: the development branch file is byte-identical to Odoo 19, option, props, template and registration alike. Even the icon markup has not joined the ongoing FontAwesome replacement wave yet.