Closed (won't fix)
Project:
Simple hierarchical select
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Jan 2013 at 08:09 UTC
Updated:
31 Jan 2013 at 13:58 UTC
when set 'Force selection of deepest level' "none" should not be available in the option list as deepest term.
| Comment | File | Size | Author |
|---|---|---|---|
| shs_none_value.PNG | 2.67 KB | kaizerking | |
| shs_conf.PNG | 7.68 KB | kaizerking |
Comments
Comment #1
stborchertSorry, but this won't work.
I've tried to implement this but it causes more problems (for example setting an initial value in the next level would require to create the next-but-one level also but this won't happen until the user selects a value).
Leaving
- None -as an option would force the user to select a value from the dropdown and ensures all preceding js magic is executed correctly.Comment #2
kaizerking commentedI ca understand that.
But can this help you Chosen ajax or chosen to hide none some how?
Comment #3
stborchertHiding the option is not the problem (from a technical perspective). The main problem here is that the user needs to manually select an option to make all the background-functions do their work (for example "display dropdown for the next level").
If I remove
- None -the user action needs to be triggered automatically for the first option and this leads to more problems ...Comment #4
kaizerking commentedHmm, ok .