Re: [jsr-314-open] sendAjaxRequest is not defined?
On 5/26/09 8:33 AM, Dan Allen wrote:
On Tue, May 26, 2009 at 11:18 AM, David Geary
<clarity.training(a)gmail.com <mailto:clarity.training@gmail.com>> wrote:
Sorry, the whole thing was my blunder. It's working fine now.
david
2009/5/26 Roger Kitain <Roger.Kitain(a)sun.com
<mailto:Roger.Kitain@sun.com>>
One thing that is wrong with your example (at least the code
snippet below) is you need to specify:
<f:ajax event="keyup".../> *not* event="onkeyup"
(using
logical names).
Now... looking over the spec - specifically - Section 10.4.1.1 I
don't see any mention of this. So, I'm adding it to the errata.
Not sure how your example is working with "onkeyup".
Sorry, that was a typo.
Could we just support both? It really depends on how you read it, but
onkeyup and keyup should be interchangeable. I guess implementations
could add this as an extension (to avoid such typos).
I'd originally argued for supporting the "on" version of the names, but
the argument that carried the day was that the actual name of the event
would be both more concise, and more accurate.
The idea of supporting both is interesting (be liberal in what you
accept, after all), I don't think that it would cause any name conflicts.
However, at least in this case, the documentation is quite clear on this
point:
The DOM event name is the actual DOM event name (for example: "click")
as opposed to (for example: "onclick").
I suspect, however, it may be better to wait and see if this is a pain
point for users... It'd be easy to add this later without endangering
existing code.
Jim