[dropdown] Further enhancing automated forceSelection

[jamessampford]

Feature Request

Following #1747 being introduced to automatically ensure forceSelection is true when being generated from a select HTML field, could this potentially be expanded to see if the standard div-based (non-select) dropdown to see whether the hidden input has a required attribute?

Both of these could be further expanded by seeing whether the dropdown is within a .field that has the .required class as well

My suggestion would then be to use the below priority in determining whether forceSelection should be true:

• Does standard div-based dropdown have required attribute? [if true, stop]
• Does select dropdown have required attribute? [if true, stop]
• Is dropdown wrapped in a field with required class?

[lubber-de]

The coder, who prepared the dropdown HTML does already know if the input has a required attribute and would declare forceSelection accordingly.

If we would add code to auto adjust the setting....we would basically make the (manual) setting obsolete.... I don't feel we should auto adjust this.

[jamessampford]

The coder, who prepared the dropdown HTML does already know if the input has a required attribute and would declare forceSelection accordingly.

Wouldn't the coder therefore know this when creating select then, making that part of the PR not needed? Just seems more logical to make it applicable to both ways of generating the dropdown

Similarly, if a select HTML field is wrapped in a .field which has .required then this would also help if the required attribute wasn't applied for some reason (likely forgotten)

[lubber-de]

I still would make this optional, so we could think of adding auto as a valid value for forceSelection which in turn would do the above suggested checks

[jamessampford]

Having an auto setting value makes sense to me 😀