Changes between Initial Version and Version 4 of Ticket #15213


Ignore:
Timestamp:
Feb 26, 2013, 3:46:27 AM (7 years ago)
Author:
bill
Comment:

I attached a test case.

On back then forward, srcNodeRef.value is "hello" (or whatever the user typed), but srcNodeRef.attributes[] doesn't contain "value", so the parser doesn't pick it up. Doug - Did you assign this to me because you thought it was a parser issue? It doesn't seem like the parser should handle this special case, although I guess it's debatable.

It seems like TextBox should just be checking for srcNodeRef.value, and using it if defined. If a value is also defined in the markup, and/or passed to the constructor, not sure which should take precedence. Perhaps TextBox should have a markupFactory() method that looks at params.value and srcNodeRef.value and decides which to use?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15213

    • Property Status changed from new to assigned
    • Property Cc Kitson Kelly added
    • Property Component changed from General to Dijit - Form
    • Property Summary changed from dijit.form.TextBox / ValBox does not hold values on iPad / iPhone "back" to TextBox: does not hold values on "back"
    • Property Owner set to Douglas Hays
  • Ticket #15213 – Description

    initial v4  
    11Make a regular html form with a regular text input. Touch submit, touch back. The value you typed remains there.
    22
    3 Then put a dijit.form.TextBox or val box and do the same. The dijit widget has "autocomplete=off" on it, and this causes a different behavior on iphone / ipad. I have created my own widget with my own template that doesn't have this, but this is to let people know if they are struggling and hopefully in the future we can lighten the markup delivered on the form widgets.
     3Then put a dijit.form.!TextBox or val box and do the same. The dijit widget has "autocomplete=off" on it, and this causes a different behavior on iphone / ipad. I have created my own widget with my own template that doesn't have this, but this is to let people know if they are struggling and hopefully in the future we can lighten the markup delivered on the form widgets.