[Prototype-core] Ajax.Responders.register for onFailure event

Hello Prototypers, Any reason why the Ajax.Responders does not support the registration of handlers for onFailure event? cheers -- mona --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Prototype: Core group. To

[Prototype-core] Re: Ajax.Responders.register for onFailure event

. cheers -- mona On Mon, Sep 28, 2009 at 11:35 AM, Mona Remlawi mona.reml...@gmail.com wrote: Hello Prototypers, Any reason why the Ajax.Responders does not support the registration of handlers for onFailure event? cheers -- mona --~--~-~--~~~---~--~~ You

[Prototype-core] omni-completion

Hello Prototypers, Wondering if a syntax/autocomplete files for Vim omni-completion exist out-there for Prototype. It will be swell to have. cheers -- mona mreml...@optaros.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

[Prototype-core] Ajax.Responders.register an onFailure

Hi Prototypers, It would be nice to be able to register an onFailure handler using the Ajax.Responders.register method. Now, one has to: Ajax.Responders.register({ onComplete: function(request) { if(request.success() === false) { // failed, what do u wanna do }

[Prototype-core] Re: Ajax.Responders.register an onFailure

patch in the ticket while waiting for the custom events to show. On Oct 29, 8:46 am, Mona Remlawi [EMAIL PROTECTED] wrote: Hi Prototypers, It would be nice to be able to register an onFailure handler using the Ajax.Responders.register method. Now, one has to: Ajax.Responders.register

[Prototype-core] Re: Bug : Object.isNumber() and Hash.toQueryString()

why go throw all this complexity when javascript has a native isNaN function... On Wed, Oct 8, 2008 at 6:40 PM, Tom Gregory [EMAIL PROTECTED] wrote: Thanks for the reply. I realize I don't get a vote here, but IMHO it either needs to be a) well documented that Object.isNumber( new

[Prototype-core] Element#getOffsetParent and Element#viewportOffset IE error

I got a the same error described in the following ticket when I added a DOCTYPE to the HTML http://dev.rubyonrails.org/ticket/11473 The patch is dated 6months old, so I'm not sure if it also applies to the recent protoype 1.6.0.3. please advise /mona

[Prototype-core] Re: Element#getOffsetParent and Element#viewportOffset IE error

-cloneposition-problem-in-ie7 Aren't there unit tests for this now? -- Rod On Oct 7, 8:37 pm, mona remlawi [EMAIL PROTECTED] wrote: I got a the same error described in the following ticket when I added a DOCTYPE to the HTMLhttp://dev.rubyonrails.org/ticket/11473 The patch is dated 6months old

[Prototype-core] element.descendants in v1.6.0.3

dear prototypers, lately we upgraded to 1.6.0.3 and I noticed that item.descendants now defaults to 'undefined' rather than an $A(). i guess you would agree that this is somehow incovenient. any plans on a quick fix? /mona --~--~-~--~~~---~--~~ You received this

[Prototype-core] Re: element.descendants in v1.6.0.3

.. and already patched! many thanks On Mon, Oct 6, 2008 at 4:34 PM, kangax [EMAIL PROTECTED] wrote: On Oct 6, 10:04 am, Tobie Langel [EMAIL PROTECTED] wrote: That works for me. Could you please post a failing test case (and open a bug report). Thanks, Tobie Filed a somewhat