The specified "default value" in a custom variable request is currently never used. What happens is that the first value with no constraints effectively becomes the default. diverweb tends to structure its requests such that this ends up with the desired result, but that's by happenstance rather than design. We really ought to make use of the actual information we requested.
What should be done:
Store the default value name.
Go through all the value definitions and apply them (IGNORING any with null definitions).
After all value definitions are parsed, any remaining NULLs are assigned the default value.
The specified "default value" in a custom variable request is currently never used. What happens is that the first value with no constraints effectively becomes the default. diverweb tends to structure its requests such that this ends up with the desired result, but that's by happenstance rather than design. We really ought to make use of the actual information we requested.
What should be done: