field_float_scannable

The whole widget:

export class FloatScannableField extends FloatField {
    static template = "barcodes.FloatScannableField";
    onBarcodeScanned() {
        this.inputRef.el.dispatchEvent(new InputEvent("input"));
    }
}

export const floatScannableField = {
    ...floatField,
    component: FloatScannableField,
};

It extends the standard float field and spreads the float descriptor, so every float option carries over. The one addition is onBarcodeScanned, which fires a synthetic InputEvent on the field's own input element.

That is a deliberate trick. A scanner types into the page faster than a human, and some of Odoo's input plumbing only reacts to real input events. Dispatching one manually makes the rest of the field machinery notice the value that just arrived.

This is a quantity box on a warehouse screen that keeps up with a scanner. Without it, a scanned quantity can land in the DOM without the field noticing, and the user saves a number that was never registered.

Because standard Odoo never used it, the question is only whether your own views do. If they do, an Odoo 20 upgrade removes the widget and the field reverts to a plain float. It will still accept typed input; it just stops reacting to scans the way it did.

On a quantity field, in Odoo 19:

<field name="quantity" widget="field_float_scannable"
       options="{'digits': [16, 2]}"/>

In Odoo 20 that same line finds no registration and falls back to the field's default rendering.

Removed. The registration is not on the 20.0 branch and the source file is gone.

There is no replacement widget. The barcode module's other field widget, barcode_handler, was removed in the same release, and barcode handling moved into the services registry as barcode_handlers, which acts on the interface through macros rather than through a field.

A view still carrying this widget will log a missing-widget warning in the browser console and render the field with its default float widget. Values still save; only the scan reaction is lost.