Hi DAW,
Currently if a DEO (webform, webedit, etc) is set to pbEnabled to False (or more precisely DD_NOENTER = True)
The WAF generates a disabled="disabled" property for the element
Example:
Code:
<input name="oCUST_TOTAL_AMT" value="" id="_df_352" placeholder="" disabled="disabled" tabindex="-1" title="" class="dfData_BCD" style="-moz-user-select: text;" maxlength="1048576" type="text">
<textarea name="oCUST_POST_ADDR1" placeholder="" disabled="disabled" tabindex="-1" title="" style="height: 305px; -moz-user-select: text;" class="dfData_Text" maxlength="50"></textarea>
Is disabling an input element really necessary ? Why not use the readonly property instead but use the same colour schema as the disabled elements (grey background) ?
Code:
<input name="oCUST_TOTAL_AMT" value="" id="_df_352" placeholder="" readonly="yes" tabindex="-1" title="" class="dfData_BCD" style="-moz-user-select: text;" maxlength="1048576" type="text">
<textarea name="oCUST_POST_ADDR1" placeholder="" readonly="yes" tabindex="-1" title="" style="height: 305px; -moz-user-select: text;" class="dfData_Text" maxlength="50"></textarea>
The advantage of using the readonly property:
- The mouse/finger still works on the input element - select/copy - wherelse the a disabled element has no mouse interaction at all.
- Read only forms/elements can receive focus but skipped on tabbing, therefore works well when you have a dynamically enable/disable forms when focus changing - currently if you disable a form as focus is being changed (onPostFind) - the WAF loses the focus.
I'm not a "Web" developer - so would like feedback on why disable is better than readonly.
Thanks