many2many_tags_color_dot

The standard Tags widget renders each tag as a filled pill. On a dense form that is a lot of color competing with the rest of the screen. This widget keeps the color as information but demotes it visually: a small dot carries the color, and the label sits next to it as ordinary text.

It is a thin subclass. The descriptor spreads many2ManyTagsField, so every option the Tags widget supports, including the new Odoo 20 tag_limit and on_tag_click, is available here too.

The one behavior it adds for itself is how clicking a tag is handled, and that is where the interesting part is.

This is a readability decision. Tag colors are useful for grouping at a glance and terrible when a record has eight of them and the form turns into a paint chart.

Dots keep the grouping signal and give the page back its hierarchy. On a record where tags are secondary information rather than the point of the screen, that is usually the right trade.

Dots with colors from an integer field on the tag model:

<field name="tag_ids" widget="many2many_tags_color_dot"
       options="{'color_field': 'color'}"/>

Making a tag click open the tag record, through the undocumented option:

<field name="tag_ids" widget="many2many_tags_color_dot"
       options="{'color_field': 'color', 'can_open': True}"/>

This is ignored, because the widget discards the inherited value:

<!-- on_tag_click is deleted before this widget sets its own -->
<field name="tag_ids" widget="many2many_tags_color_dot"
       options="{'on_tag_click': 'edit_color'}"/>

The whole addition is five lines:

extractProps({ attrs, options, string, placeholder }, dynamicInfo) {
    const props = many2ManyTagsField.extractProps(
        { attrs, options, string, placeholder }, dynamicInfo
    );
    delete props.onTagClick;
    if (options.can_open) {
        props.onTagClick = "open_form";
    }
    return props;
}

Read the order carefully. It runs the parent's extraction, then unconditionally deletes onTagClick, then sets it again only if can_open is truthy.

Two consequences. First, can_open is a real option that appears in no option list, no documentation and no Studio panel, because this widget declares no supportedOptions of its own and inherits the parent's list, which does not mention it.

Second, the parent's on_tag_click option is unreachable here. Whatever you set, the delete removes it. So the Odoo 20 ability to make a tag click open the color editor, which many2many_tags supports, cannot be used with color dots. Given that the dot is the color, that is a defensible design decision, but it is not one you would discover from the options list.

By default, with can_open unset, clicking a tag does nothing at all.

Introduced in Odoo 20. Odoo 19 has no color dot variant, so the closest equivalent there is the plain Tags widget with colors, which renders filled pills.

It arrives in the same release where many2many_tags itself changed noticeably: edit_tags and no_edit_color were replaced by a single on_tag_click selection, and a tag_limit option was added that shows a counter past a threshold. Because this widget spreads the parent descriptor, tag_limit works here, and it pairs well with dots on a crowded record.