Mandatory select listbox has 'select...' option

Using an older version (2.3) but mandatory select list shows default value.

For example, in a list of provinces is this entry:

ON|Ontario

For default value I've entered:

ON

The user sees 'Ontario' in the select list.

Hi @BWPanda, I totally agree with you. Mandatory select field should not render "select..." as an available option.
Same issue on version 6.x-2.9, though.

@Maintainers of Webform: Wouldn't you consider this as a bug?

Thanks,

I'd be willing to remove the "select...", but only if the field is both mandatory AND a default value is already provided. Often it's helpful to not provide use the first value on a required field because it tends to suggest to the user that the first answer should be used, which might not be the case in a situation where you're asking for a user's opinion for example (i.e. Bad, Okay, Good, Great).

The $component['value'] property is the default value for a field.

Perfect BWPanda, committed to all branches.

Hi,

Sorry to open this back up, but I'm a bit baffled as to why the 'Default Value' for select component in a webform doesn't become the default value? 'select...' is neither useful, nor specific. We have the option to fill out a default value, so why not have that drop directly into the first slot of a select list? I tried poking into the code but it's a bit outside my capabilities. This would seem to solve some of the other select default issues that have been raised here.

Is there a reason not to do this?

Hi teamA,

I agree with you. It would make sense if you fill out a default value that it would override the 'select...' value.

In the meanwhile I found out that you can change the 'select...' value into anything else with a string override. This solves the problem for me for now.

Yet, an override by the default value would make more sense to me...

Cheers,
Danny

I agree with teamA - the correct approach is for the default value, if set, to be presented to the user when completing the form. Otherwise there is no benefit to having a default value option.

In my view this is a bug, so I'm reactivating the issue.

Otherwise there is no benefit to having a default value option.

If you set a default and make the field required, the "select..." option disappears. Otherwise the user may need an option to not select anything (or leaving it blank).

I have a mandatory select field that has as default value a profile token: %profile[profile_title]

This field is filled in by registered users but not by anonymous users, so the default value does not apply to them.
So in this case the "select..." option must appear.

I noticed this issue after upgrading from 2.9 to 3.0 beta and I opened an issue for this.

Maybe the issue http://drupal.org/node/853836 also applies to this one.

Reopen...?

Thanks for opening the new issue. Let's discuss your new issue there.