CopyClipboardButton

Odoo ships one source file with three clipboard widgets. CopyClipboardChar and CopyClipboardURL display the field's value with a copy control attached. This page's widget is the third and the odd one out: CopyClipboardButton shows a standalone button and never displays the value. Click it, and the field's raw content is on the clipboard; a brief "Copied" confirmation replaces the label.

That makes it the right choice for values that are long, ugly, or pointless to read: feed URLs, API keys, webhook endpoints, tokens. Core's canonical use is the product feed URL in website_sale, a generated address nobody benefits from seeing, placed in the form's button box as a simple "Copy URL" action.

The whole rendering is one template line with a guard: if the field has no value, the widget renders nothing. There is no empty state to style and no dead button to explain; the control simply appears once the value exists.

The difference between "select the URL, Ctrl+C, hope you got all of it" and one labeled button sounds trivial until you watch non-technical users handle machine-generated strings. Partial copies of feed URLs and keys are a real support category, and this widget removes the failure mode by never letting the user near the raw text.

It also has a mild security-adjacent benefit: values that should not be casually shoulder-surfed, tokens, private links, can be made copyable without being displayed. That is presentation-level discretion, not protection, since the value still travels to the browser and sits in the DOM props, but it keeps screens and screenshots clean.

Design-wise, treat it as an action, not a field. Core places it in the button box with a verb label via string. A copy button lost in the middle of a field grid with the default "Copy" label tells the user nothing about what they are copying; "Copy feed URL" in the header does.

As core uses it, in the button box

<div name="button_box">
    <field name="url" string="Copy URL" widget="CopyClipboardButton"/>
</div>

Secondary styling with the 19-new option

<field name="api_key" string="Copy key"
       widget="CopyClipboardButton"
       options="{'btn_class': 'secondary'}"/>

The value slots into btn-{value}, so any Bootstrap button flavor works: secondary, outline-primary, link.

Conditionally disabled

<field name="share_url" string="Copy link"
       widget="CopyClipboardButton"
       disabled="not is_published"/>

The expression is evaluated per record, so the button greys out until the record is published.

Reading the file end to end turns up details that matter in practice.

Empty means invisible. The Button template is guarded by t-if="props.record.data[props.name]". The sibling widgets keep their field visible when empty; this one vanishes entirely. If your layout needs a stable placeholder, reserve the space or show a muted note conditionally.

It copies exactly what is stored. The template hands record.data[name] to the copy component. There is no formatting pass, no URL prefixing (unlike the display behavior of the URL widget family), no trimming. Whatever the database holds is what lands on the clipboard.

Clipboard needs a secure context. The underlying CopyButton uses the async browser clipboard API, which browsers only expose on HTTPS or localhost. On a plain-HTTP staging box the button renders and does nothing, which reliably files a false bug.

The type in the CSS hook is the field type. The class is o_btn_{type}_copy where type is the field's technical type, so a char field yields o_btn_char_copy. Useful for targeted styling, confusing if you expected the widget name.

Unsupported types are not enforced. Unlike its siblings, the Button descriptor declares no supportedTypes, so nothing stops you putting it on, say, an integer field; it will copy the raw value. Treat char and text as the intended surface.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. These notes are read from the public development branch, which is unstable until feature freeze; we re-verify against the shipped release.

For the Button variant specifically, behavior is unchanged: same template guard, same btn_class option with the primary default, same registration. The visible master changes hit the siblings: the Char and URL variants' copy icons switch from Font Awesome clipboard and link glyphs to the new assignment icon set, and their attached-button styling moves from btn-sm to btn-link btn-link-inline. The file also picks up the framework-wide props-validation migration, which exports the shared props for reuse but changes nothing in XML.