Richfaces 4.5.13 inputspinner problems

[wish79]

Hello, when i upgrade to RC 4.5.13 i have the following problem : if i try to set the numeric value directly by hand (manually) i have the following problems(richfaces.queue: ajax submit error: Cannot read property 'id' of null) in a4j:log and any action stopped wprking. but if i back to RC 4.5.12 every thing is working fines. Regards Mohammad Weshah 

[michpetrov]

What browser are you using?

<rich:inputNumberSpinner value="#{bean.number}">
    <a4j:ajax />
</rich:inputNumberSpinner>

I see no error when I try this. 4.5.13 doesn't contain any changes directly related to inputNumberSpinner.

[wish79]

   try with event="blur"

<rich:inputNumberSpinner value="#{bean.number}"> 

  <a4j:ajax event="blur" /> 

</rich:inputNumberSpinner>

[michpetrov]

Still no error, have you tried just the sample? There might be something else on your page that's causing it.

[wish79]

still the problem exist in

Richfaces 4.5.13

Richfaces 4.5.14

Richfaces 4.5.15

but if you back to Richfaces 4.5.12 it is working, again the problem when add:

<rich:inputNumberSpinner>

  <a4j:ajax event="blur"  />

</rich:inputNumberSpinner>

when just onblur fire the following log shows on a4j:logn and any ajax action on the page disable (button ,etc..)

debug[22:23:52.499]: New request added to queue. Queue requestGroupingId changed to

debug[22:23:52.503]: Queue will wait 0ms before submit

debug[22:23:52.504]: richfaces.queue: will submit request NOW

warn [22:23:52.522]: richfaces.queue: ajax submit error: Cannot read property 'id' of null

debug[22:23:52.524]: richfaces.queue: Nothing to submit

but if you change the event to change it is working fine

<rich:inputNumberSpinner>

  <a4j:ajax event="change"  />

</rich:inputNumberSpinner>

or if you back to Richfaces 4.5.12 it is working

Please advice

Regards

Wish79

[michpetrov]

Still can't reproduce it, have you checked where the error comes from? What browser and JSF version are you using? If you can create a project I can deploy I can take a look at that (there might be an issue with event handlers other than "onchange" but I'm not getting any errors and the value updates correctly).