Changes between Initial Version and Version 1 of Ticket #17160


Ignore:
Timestamp:
May 17, 2013, 2:15:53 AM (8 years ago)
Author:
bill
Comment:

It would be better if you could attach a full (but minimal) test case using the "attach file" button.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #17160

    • Property Owner changed from bill to Douglas Hays
    • Property Milestone changed from tbd to 1.9.1
    • Property Component changed from Dijit to Dijit - Form
    • Property Summary changed from NumberSpinner associated input is not initialized with provided value to [regression] NumberSpinner: associated input is not initialized with provided value
  • Ticket #17160 – Description

    initial v1  
    1 While the NumberSpinner displays correctly, the input associated with it is initialized with an empty value when the page is loaded, instead of the value provided with the 'value' property. That input is initialized only once a key press down event is received. So if the form is submitted without interacting with the NumberSpinner, that input is submitted with an empty value. However, if the value is changed, either by clicking on the spinner arrows, or by typing the new value, then it works correctly.
     1While the !NumberSpinner displays correctly, the input associated with it is initialized with an empty value when the page is loaded, instead of the value provided with the 'value' property. That input is initialized only once a key press down event is received. So if the form is submitted without interacting with the !NumberSpinner, that input is submitted with an empty value. However, if the value is changed, either by clicking on the spinner arrows, or by typing the new value, then it works correctly.
    22
    33Here is the code I use:
    44
    55In the script tag in the header:[[BR]]
     6{{{
    67dojo.require("dijit.form.NumberSpinner");
     8}}}
    79
    810In the body:[[BR]]
     11{{{
    912<div id="spinnerId"></div>
    1013<script type="text/javascript">
     
    1619      style: "width:3em"
    1720   }, "spinnerId" );
     21}}}
    1822</script>
    1923
     
    2428
    2529Interacting with the spinner modifies the input:[[BR]]
     30{{{
    2631<input type="hidden" name="spinnerVal" value="8">
     32}}}
    2733
    2834In that case, it works correctly.