----
Buttons created with the BUTTON element function just like buttons created with the INPUT element, but they offer richer rendering possibilities: the BUTTON element may have content. For example, a BUTTON element that contains an image functions like and may resemble an INPUT element whose type is set to "image", but the BUTTON element type allows content.
---
So, it is a IE bug for me. If you make a submit button, it should rather not send its value unless it is pressed. But IE sends the value, what completely confuses Woody - it is impossible to determine which button was pressed. It doesn't matter if you use client-side JS.
Regards, Marcin Okraszewski
Can we say it is a IE bug? What do the HTML specs say? Is client-side JS processing used?
I'm using cforms, too, but I never use any of the features that require a JS capable client. (I had very good reasons for that solemn promise, never again relying on client capabilities beyond HTML.)
/Leo
On Apr 10, 2004, at 3:56 PM, Marcin Okraszewski wrote:
The more I'm into creating webapps the more I'm fed up with IE. The worst is that users even don't have the faintest idea how many problems people have because they use IE.
Marcin Okraszewski
Be sure, you are not the only one:
http://marc.theaimsgroup.com/?t=107962802400002&r=1&w=4
I figured out the problem, suggested a solution (but have not thought deeper about it), but did not do anything on it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
