You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So while you technically can pass true or false, both values exhibit the same behavior, disabling the field. The only way to keep the field enabled is to exclude the attribute entirely:
<cfinput name="foo">
I wanted to PR this, but at a glance it looks like this isn't handled in the schema, so hoped someone could chime in on the correct approach here.
Tested on CF 2018.
The text was updated successfully, but these errors were encountered:
Currently
cfinput
showsdisabled
as aboolean
. However, that's not actually the behavior. Both of these result in a disabled input field:This is because ColdFusion treats this attribute the same as HTML does; its presence at all activates its effect:
https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-tags/tags-i/cfinput.html
So while you technically can pass
true
orfalse
, both values exhibit the same behavior, disabling the field. The only way to keep the field enabled is to exclude the attribute entirely:I wanted to PR this, but at a glance it looks like this isn't handled in the schema, so hoped someone could chime in on the correct approach here.
Tested on CF 2018.
The text was updated successfully, but these errors were encountered: