CFINPUT type="radio" w/ "value" requires "label"

[Iceborer]

On a Flash form, when you specify type='radio' and value='whatever', the value
of the 'value' attribute will be displayed as a label if no 'label' attribute
is specified. I got around this by specifying label=''. Bummer
<sarcasm>Hopefully this is just a problem in the 7.0 Beta version and will be
fixed before the production release</sarcasm>

[Mike Nimer]

Why do you want multiple radio buttons with no labels, how does the user
know what each radio button means?

With that said, this is the intended behavior. And if you don't want a
label, you are doing the right thing by setting an empty label="" for the
radio button.

hth,
---nimer


"Iceborer" <webforumsuser@macromedia.com> wrote in message
news:cv0cqv$9qb$1@forums.macromedia.com...

> On a Flash form, when you specify type='radio' and value='whatever', the
> value
> of the 'value' attribute will be displayed as a label if no 'label'
> attribute
> is specified. I got around this by specifying label=''. Bummer
> <sarcasm>Hopefully this is just a problem in the 7.0 Beta version and will
> be
> fixed before the production release</sarcasm>
>

[Iceborer]

Why do you want multiple radio buttons with no labels, how does the user know
what each radio button means? Imagine that I have 3 options from which the
user can select (in this case requesting vendor quotes): Give me a price quote
for: (o) EXACTLY [InputBOX] Units (o) [InputBOX] Units plus next [InputBOX]
Price Breaks (o) All Price breaks from [InputBOX] Units to [InputBOX] Units
Now you?ll see my dilemma. In any case, it is bad for two reasons: (1) It
departs in functionality from normal HTML radio buttons in which the 'value'
attribute is used to differentiate between radio buttons in a group (same name,
different value) and not to provide descriptive inline text. In other words to
pass the ?value? to the receiving form. (2) It makes a wholly inaccurate
assumption that the user wants ANY label on the radio button. There are any
number of option values or layout choices which might make this a bad thing
(TM). In addition, there is already a 'label' attribute which allows
specification of the label to be displayed-- let it do its job. I don't think
that insisting that a user have a label on his radio buttons makes any sense.
I left out the OPTIONAL ?label? attribute because I didn?t want a label, not
because I wanted the software to guess at one for me. BTW, if this is the
intended behavior, and I argue strongly against that, DOCUMENT IT! Which is
more intuitive, ?leave ?label? off, get no label? or ?want no label, specify
?label=??? otherwise you?ll get ?value? as label??