Hi,
SELECT fields don't get initialized in the same way as INPUTs:
[- $fdat{test1} = 100 -]
<input name=test1 value=3>
would show 3 (which is correct and intuitive I believe) while
[- $fdat{test2} = 100 -]
<select name=tst2>
<option value=222>222
<option value=333>222
<option selected value=444>444
</select>
would show 100 instead 444 which is a bit confusing.
Even more confusing is that $optDisableTableScan disables SELECT
handling too: sometime I need to turn off table scan (often because
table head and foot are in different files), but I still want Embperl to
take care of the form handling. Maybe $optDisableTableScan could disable
OL and UL together with tables stuff, but disabling SELECTs that way is
a bit counter-intuitive.
- Robert
P.S. I'm running with EMBPERL_OPTIONS = 16
SELECT fields don't get initialized in the same way as INPUTs:
[- $fdat{test1} = 100 -]
<input name=test1 value=3>
would show 3 (which is correct and intuitive I believe) while
[- $fdat{test2} = 100 -]
<select name=tst2>
<option value=222>222
<option value=333>222
<option selected value=444>444
</select>
would show 100 instead 444 which is a bit confusing.
Even more confusing is that $optDisableTableScan disables SELECT
handling too: sometime I need to turn off table scan (often because
table head and foot are in different files), but I still want Embperl to
take care of the form handling. Maybe $optDisableTableScan could disable
OL and UL together with tables stuff, but disabling SELECTs that way is
a bit counter-intuitive.
- Robert
P.S. I'm running with EMBPERL_OPTIONS = 16