> it separates the name of the fuseaction from the value on the button.
Yeah, when I read this last night (i.e. when you wrote it, I'm in NZ) I
thought, mmm, big deal. What I had been doing was just using this sort of
thing in the fusebox:
<cfcase value="Review Order,Change my items">
So that would represent two different submit buttons on different pages that
call the same FuseAction. It works fine, but it means that each FuseAction
has more than one name, and they're not good names (I have another one
called "Proceed to Checkout > >"!!). I have come to think that's a bad
thing. Another bad thing is that FuseAction names and button names should be
independent, and mine are not. So I'm going to go into my code (I haven't
done much Fusebox yet) and change it all.
It's bloody stupid that in HTML you can't separate the caption of a button
from the value it passes though, I have to say. Another annoying thing is if
you have a "Cancel" button on a form that is using CF's built-in server-side
validation, CF still validates it. Yet another annoying thing is that if you
use <button> instead of <input> so that you can create rich buttons (I wrote
a little tag that detects browsers and serves up a plain buttons to older
browsers), then IE submits the values of all the submit buttons, not
differentiating which one you pressed.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
