On Tue, 2008-07-08 at 04:32 +0200, Pascal MARCELIN wrote:
> II was recently asked by an old lady (over 80) to "reproduce" the
> interface of a MUIbase project she's been using for years to handle
> yer web site data directly over the net rather than having to export
> it to mysql using MUIbase. I am in the phase where I search for handy
> yet stable and preferably universal tricks to do so in a way that will
>; save me work.
If you're looking for stable and universal, that's not the way to go.
Having a group of input type=image elements is making a form with
multiple submit buttons, that's never been a wise move. Particularly if
you want those submit buttons to each behave differently.
>;> b. When using images, it's the co-ordinates that convey the information
>>; about the user clicking on them. You appear to be parsing for the
>> wrong data.
> Apparently wrong for IB, MS and Opera but right for FireFox, Konqueror,
> Safari, old Mozzilla...
Don't confuse browser behaviour with right and wrong handling of HTML.
When you build things relying on faults or undefined behaviour, you're
letting yourself in for trouble. The main point of using images in
inputs is to convey something about where in the image you clicked on.
If you don't care where, then just go for getting any result back,
ignoring the numbers. If you're hoping for different name= attributes
values to come back, you should probably give each button different
names, major.minor style, perhaps.
> Moral of the story 
knowing how to build nuclear weapons would not help
>; me slam a mosquito that annoys me when I'd like to sleep 
You could make them glow in the dark so they're easier to aim at...
Regards,
Tim.
.