Lightweight interface components for exploring data and building interactive displays

Mike Bostock

Observable

Hello, Inputs!

Button Input / Observable Inputs

Toggle Input / Observable Inputs

Checkbox Input / Observable Inputs

Date Input / Observable Inputs

Radio Input / Observable Inputs

Range Input / Observable Inputs

Select Input / Observable Inputs

Text Input / Observable Inputs

Textarea Input / Observable Inputs

Color Input / Observable Inputs

File Input / Observable Inputs

Table Input / Observable Inputs

Search Input / Observable Inputs

Synchronized Inputs

Legacy Inputs

Form Input / Observable Inputs

Observable Inputs

Are you planning to add an example for the template callback?

Fabian Iwand

Would you like to suggest one? I don’t have a use case in mind.

Common use cases would be horizontal alignment, <fieldset>, <detail>, etc.. I have a few older examples of varying complexity for native inputs in https://observablehq.com/d/852ff200776cb9f4

Do you want to limit the example to Inputs widgets, or are you open to including native inputs (minus native button, checkbox, radio)?

https://observablehq.com/@ambassadors/whats-that-noise now uses Inputs.form() with custom template callbacks.

It would be great to add some documentation here, or on the Synchronized Inputs page, about how to bind (or otherwise manipulate) a field on a form. It wasn't clear how to do so at first.

For example, https://observablehq.com/d/dca8540d04be23c8

(admittedly, I skipped most of the docs like views which later helped me figure it out)

Joey Pereira

Is it possible to use submit:true for the whole form?

Not out of the box. You might find this helper useful: https://observablehq.com/@mootari/inputs-submit

Purpose-built for displays of data