W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2008

Re: FORM successful submit element?

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Sun, 10 Aug 2008 22:26:11 +0100
To: "Garrett Smith" <dhtmlkitchen@gmail.com>
Cc: "DOM mailing list" <www-dom@w3.org>
Message-ID: <op.ufowhxtsjz3wb9@mors>

How is that toString issue related with your original message?
Anyway, if you really want to blame someone, join the whatwg mailing lists  
and contribute to the WF2 specification. Currently websites resort to  
javascript hacks to redirect a form submit to different urls. Useless I  
know.


On , Garrett Smith <dhtmlkitchen@gmail.com> wrote:

> On 8/10/08, Joćo Eiras <joao.eiras@gmail.com> wrote:
>>
>>  Hi.
>>  Opera probably gives the info you want because Opera supports WebForms  
>> 2,
>> and in web forms you can have several submit buttons with different  
>> actions.
>> It seems the other browsers have this behavior undefined.
>>
>
> Really?
>
> I guess the only use case for that would be submitting to different  
> domains.
>
> Taking that successful submit param on the server, all that is needed
> is a simple RequestDispatcher.
>
> WF2/HTML5 - Too many new features while there are things in HTML that
> still don't work in IE or Webkit.
>
> Opera needs to get some basicthings in order before implementing these
> new things. For example:
>
> <form><input name="toString"></form>
>
> javascript:try{ alert(document.forms[0].elements); } catch(ex) {  
> alert(ex); }
>
> Opera: Error: Object doesn't implement [[Call]].
>
> Because Opera tries to call the 'toString' property off of the
> 'elements' object. It should not do this, but should have an internal
> method that safely converts the HTMLCollection to a string.
>
> Garrett
>
>>
>>
>>  On , Garrett Smith <dhtmlkitchen@gmail.com> wrote:
>>
>>
>> > How to identify the submit button when a form was clicked?
>> >
>> > The form below has three elements that can be used to submit the form.
>> > If the form is submitted, it could be that one of the buttons would be
>> > the cause, and, in that case, that button should be included in the
>> > query string.
>> >
>> > The browsers seem to have an internal mechanism for determining which
>> > button is successful. Is the form's successful button exposed in the
>> > DOM?
>> >
>> > <form action="" id="theForm">
>> >  <input name="text" value="blah">
>> >
>> >  <input id="submit" name="submit" value="submit form here"  
>> type="submit">
>> >  <input id="submit2" name="submit2" value="submit form there"
>> type="submit">
>> >  <input id="submit3" name="submit3" value="submit form elsewhere"
>> > type="image" alt="[submit elsewhere]" src="missing.null">
>> > </form>
>> > <script>
>> > document.getElementById('theForm').onsubmit = function(e)
>> {
>> >   alert(e.relatedTarget.type);
>> > };
>> > </script>
>> >
>> > Opera: "image", et c.
>> > IE8, FF3, Safari 3: Error
>> >
>> > When the form is submitted, how to determine if and which submit input
>> > was the cause?
>> >
>> > Garrett
>> >
>> >
>>
>>
>>
>>
Received on Sunday, 10 August 2008 21:27:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:59 GMT