Type directly in control for single-select fields, rather than having a separate input in the dropdown

[elis]

For some reason I can't seem to find anywhere in the docs nor in the code itself an option to make a single value (where you have the text input below the button/select that is being clicked) appear as the multiple value select, where there is no additional button or styling to the text box.

[kevin-brown]

You should be able to do this using a hidden tag with { multiple: true, maximumSelectionSize: 1 }.

Edit: And there is actually no reason why you wouldn't be able to do this with a <select> tag, except the data that is being sent to the server will be formatted as a multiple select.

[elis]

That's just limits to one tag, not a single input :/ :+1:

And adds "you can only select 1 item" while still inside the text box.

[ivaynberg]

whats the difference between allowing a single choice vs single input?

[elis]

The way it looks.
The UI is different in the two cases, and the UI should be a matter of
choice for either case, not based on the type of select/input you want to
use (multi/single).

-Eli

On Tue, May 28, 2013 at 10:46 PM, Igor Vaynberg notifications@github.comwrote:

whats the difference between allowing a single choice vs single input?

—
Reply to this email directly or view it on GitHubhttps://github.com/ivaynberg/select2/issues/1345#issuecomment-18575081
.

[ivaynberg]

how is the ui different? what i suggested will make it look like multiselect but only allow a single selection...

[elis]

@ivaynberg but it will still show a 'tag' inside the input box instead of showing the text like simple text inside simple input box.

What I mean is:

• Open this: http://ivaynberg.github.io/select2/index.html
• Navigate to "Placeholders" and look at the two different input/select boxes
• Visual difference no' 1: The "Single Value" has a drop-down like UI, while multi-select has an input[type=text] like UI
• Select an item in the first select, and select one item in the second select
• Visual difference no' 2: Even with a limit of 1 item for multi-select the input box will behave as "multi-select", and on top of that will display a warning saying that I am limited to one option only

What I want is basically to not be limited by functionality when choosing UI appearance, and not be limited by visual appearance when choosing functionality - these two should be interchangeable and unrelated to functionality.

Proposed way to handle it is allowing a flag in the options to select what type of UI should be used; First option is "drop-down" and second one is "text-input", both of which can be multi-optional or single-option.

[elis]

Can this issua be reopened since it's not closed?

[vdroznik]

I am +1 for this feature

[Antares42]

To comment on elis' post on visual differences:

• Visual difference no' 2: Even with a limit of 1 item for multi-select the input box will behave as "multi-select", and on top of that will display a warning saying that I am limited to one option only

This is important when making the UI design independent of single/multi. With the current workaround (use multi, limit to 1) one cannot exchange one choice for another, i.e. one cannot choose a different option without deleting the current option first. This may not be what the user / developer wants, because it invalidates the current "allowClear=false" behavior of the single select.

TL;DR: A multiselect with limit 1 does not emulate a singleselect with allowClear=false.

However, I'm all in favor of allowing the use of the multi-UI for singles. It's sleek, and it solves the "two-click" issue I mentioned above.

[kylemwhite]

Another +1 for this issue. Think of Google search, it's a single select without a drop-down indicator.

[janusch]

are there any workarounds or plans to implement this feature? I am also looking for an input field that can display the selected option without the additional style of the multiselect.