Why is cfform still so screwed?

I generally avoid it, but I'm working on one for this small project
because I'm already losing money on the project. It was originally set
up with a cfgrid and the problem was that when 12 rows of data were
entered in the grid, only 5 of those rows were passed to the submit
page. So I got rid of the grid in favor of simple text fields and
wanted to use cfinput to validate their being numeric. But I also
wanted to make it easier for the user by applying tab indexes to the
fields, and discovered that all the tabindex values have .0 added to
them by cfinput, which of course makes the browser ignore them. Why is
this screwed up? This is completely basic!

s. isaac dealey     434.293.6201
new epoch : isn't it time for a change?

add features without fixtures with
the onTap open source framework

http://www.fusiontap.com
http://coldfusion.sys-con.com/author/4806Dealey.htm


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:237113
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to