Creating button set causes error if other type of input with same name found

Hi LordHamwich,

Thanks for taking the time to contribute to the jQuery UI project.

This happens because the widget looks for radio buttons within the form and not within the buttonset: https://github.com/jquery/jquery-ui/blob/master/ui/jquery.ui.button.js#L33.

Why would you need multiple inputs with the same name within a form? Both values submit, but this seems like a very strange thing to be doing, and it would add a decent amount of complexity to handle for this.

Poor but known quick and easy hotfix for forcing empty value through post if no radio button is checked. Of course I got around that, but still thought that behaviour was strange.

Looking at that code, it just searches by name, right? So even a SPAN with a same name is causing the same errors and glitching.

http://jsfiddle.net/vpGUX/1/

Why would it even search inputs from outside of the selector element? API documentation states only that "Buttonset is used by selecting a container element (which contains the radio buttons) and calling .buttonset() ... It works by selecting all descendants and applying .button() to them".

Spans are not submittable elements and placing a name attribute on them is invalid HTML.

I'm going to close this as patcheswelcome. While technically you can have different fields in a form with the same name, I cannot think of a reason you would do this. If someone would like to change our implementation, we could look at a pull request.

If someone else on the team feels differently feel free to open this again.

#9570 is a duplicate of this ticket.

As bug #9570 states, it is an issue with the way jQuery UI does radioGroup selection. That is, there is an error is the code. Function radioGroup's purpose is to select radio inputs (as the name implies), belonging to the same name group. However, it selects all inputs of the same name (http://jsfiddle.net/AKC2v/1). Also, it does not correctly replicate behavior of HTML standards as plain HTML would handle radio group and a text input of the same name (http://jsfiddle.net/AKC2v/2).

As for the use case of applying the same name to various types of inputs, it is irrelevant. I believe that what made jQuery and jQueryUI so great is the tool set, a super set, they provided and not the ideology of how one thing should or should not be used. But not to sound like a jerk, my use of radio and input combination is as follows. I have created a metrics report tool. One of the dynamic parameters/filters that can be specified is the date range. The range consist of radio group containing today, last 7 days, month to date, year to date, previous month, and a custom date text input. When the user selects one of the radios, custom input gets disabled, when custom input is enabled, radios get deselected. This results in serialization to only one name instance.

[[Image(http://s18.postimg.org/k25k6hsex/date_filter.png)]]

Sounds pretty bad. You should make custom a radio and when it's selected, the text field is enabled.