Changes between Initial Version and Version 1 of Ticket #12116


Ignore:
Timestamp:
Dec 23, 2010, 10:59:51 PM (11 years ago)
Author:
bill
Comment:

Sounds like the same problem will happen with NumberTextBox. Perhaps it's as simple as removing type from attributeMap (well technically, it's difficult to remove it and still do inheritance, but can override the value setting it to null or undefined).

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12116

    • Property Owner changed from anonymous to Douglas Hays
    • Property Component changed from General to Dijit
    • Property Summary changed from dijit.form.CurrencyTextBox clash with <input type="number"> to CurrencyTextBox/NumberTextBox: clash with <input type="number">
  • Ticket #12116 – Description

    initial v1  
    11The following declarative widget instantiation:
    22
     3{{{
    34<input dojoType="dijit.form.CurrencyTextBox" type="number" required name="sample"/>
     5}}}
    46
    57renders correctly on Chrome 8.0.5, although we get number spinners inside the input field.
     
    911Tracing the issue through I found out why.
    1012
    11 Values from 0 to 999 are formatted without a comma but 1000 is the first value that requires one. When the new user value is being set, eventually we hit this code in "TextBox.js#_setValueAttr":
     13Values from 0 to 999 are formatted without a comma but 1000 is the first value that requires one. When the new user value is being set, eventually we hit this code in "!TextBox.js#_setValueAttr":
    1214
    1315{{{
     
    2224Looking at the rendered HTML for this widget, I see the following.
    2325
     26{{{
    2427<input class="dijitReset dijitInputInner" dojoattachpoint="textbox,focusNode" autocomplete="off"''' "type="number"''' id="dijit_form_SampleCurrencyTextBox_0" tabindex="0" aria-valuemin="-9000000000000" aria-valuemax="9000000000000" aria-required="true" aria-invalid="true" value="" aria-valuenow="NaN">
     28}}}
    2529
    2630According to the HTML5 spec (http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#number-state)