607948 - Better handle saving/searching form history for inputs with @multiple

Status: NEW

(Toolkit :: Form Manager, defect)

Description

[Mounir Lamouri (:mounir)]

Fields with the multiple attribute shouldn't have autocompletion for the entire field's value but only the currently edited token.
To do that, we should split the values when saving them and mark them as multiple. Then, when getting the values, we should only take the multiple ones.

Maybe non-multiple fields can get multiple values.

Comment 1

[Matthew N. [:MattN]]

(In reply to Mounir Lamouri (:mounir) from comment #0)
> Fields with the multiple attribute shouldn't have autocompletion for the
> entire field's value but only the currently edited token.

I'm not sure I agree as there are cases where multiple values are regularly used together and being able to complete them at once would be nice and wouldn't regress workflows based on our current behaviour. I'll admit that I've never seen UI for this from an autocomplete dropdown in the wild but I believe it's a valid use case. For example, Gmail has a (labs?) feature to suggest other people you may have missed on a recipient list if you regularly email them together. Perhaps the results for the first token could include multiple values?

> To do that, we should split the values when saving them and mark them as
> multiple. Then, when getting the values, we should only take the multiple
> ones.

I'm not sure why we would want this extra column or why we would only show the multiple ones. What is this trying to achieve?

> Maybe non-multiple fields can get multiple values.

I don't see any reason why you wouldn't want tokens that are submitted on an <input> with @multiple to be suggested in a field for an individual token. Maybe there is a use case for @multiple that I'm not thinking of. My primary examples are for choosing contact information e.g. email or telephone.