This Action fixes a few things that bug me about Freeway’s form
elements at the code level. Applied to a page, it loops through the
entire page, finds any form elements, and does the following:
Gives each form element an ID. This is automatically the same as
the field’s name, except in the case of radio buttons (which would
lead to an ID clash). Radio buttons are ID’d like this:
ClusterName_Value. IDs make it possible for JavaScript to do fun
things with form elements.
Cleans up the internals of picking lists. Each option gets a label
attribute, and empty values are given a value of nothing rather than
no value attribute at all.
Gives text fields a ‘type="text’" attribute, so they are
unambiguous. (Freeway just codes them as < input >, which makes it
harder to style them specifically using CSS.)
If anyone can think of anything else they want to add to this list,
let me know. Available here:
Great stuff Walter, I’ve added these things as suggestions on the
database.
Joe
On 26 Jun 2008, at 02:00, Walter Lee Davis wrote:
This Action fixes a few things that bug me about Freeway’s form
elements at the code level. Applied to a page, it loops through the
entire page, finds any form elements, and does the following:
Gives each form element an ID. This is automatically the same as
the field’s name, except in the case of radio buttons (which would
lead to an ID clash). Radio buttons are ID’d like this:
ClusterName_Value. IDs make it possible for JavaScript to do fun
things with form elements.
Cleans up the internals of picking lists. Each option gets a label
attribute, and empty values are given a value of nothing rather than
no value attribute at all.
Gives text fields a ‘type="text’" attribute, so they are
unambiguous. (Freeway just codes them as < input >, which makes it
harder to style them specifically using CSS.)
If anyone can think of anything else they want to add to this list,
let me know. Available here: