It is fixed in 1.4.18. It was caused by a change in Chrome (and later WebKit) behavior
On Fri, Aug 12, 2011 at 11:48 AM, Martin Makundi <[email protected]> wrote: > Hi! > > Wicket-ajax 1.4 suffers nullpointer in Chrome: > > // go through newly added elements and try to find javascripts that > // need to be executed > while (element != next) { > try { > Wicket.Head.addJavascripts(element); > } catch (ignore) { > } > element = element.nextSibling; > wicket-ajax.js:343Uncaught TypeError: Cannot read property 'nextSibling' of > null > } > > > Stranegly this nullpointer occurs only in Chrome in some very rare > situations (completely unrelated dom differences seem to make the > difference of having or not having a nullpointer here -> very > difficult to reproduce in general). > > ** > Martin > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
