Henning Koch

> I'm not sure what "feedback" means as it's a very general term not specific to loading/processing something. Unpoly uses the `{ feedback }` option to enable `up-active` and `up-loading`...

Hi @marc-mabe. Thanks for thinking about this some more. While I like the minimalism of this, here's one concern: The `[up-feedback]` attribute controls two classes: `.up-active` (for the element causing...

I couldn't understand this. Can you provide examples?

When reloading Unpoly needs an element to discover which URL to reload from, and which ETags / Last-Modified headers to send.

Expanding a bit on @kratob's comment, because it isn't well documented in Rails: If you have `class Cat < ActiveType::Record[Animal]`, the call to `Cat.human_attribute_name(:name)` will look in the following places:...

Unpoly autosubmits the form when the form's params ("form data") changes. The checkboxes have the same `[name]`. The last checked checkbox with a given name is the one that goes...

> The last checked checkbox with a given name is the one that goes into params. I didn't say this correctly. This will work for keys with an `[]` suffix,...

The `[]` suffix is a convention shared by many, but not all web frameworks. There is no web standard for it AFAIK. It would technically be possible to detect multi-selects...

> Would it be possible to add an 'up-multivalue-fields="status, xyz"' attribute to the form tag (or maybe on the inputs directly) to help unpoly out while keeping the signatures of...

A workaround for now: 1. Have your custom element implement `{ name, value }` properties 2. Push its selector to [`up.form.config.fieldSelectors`](https://unpoly.com/up.form.config#config.fieldSelectors) Unpoly should eventually support custom form-associated elements, either via...