> Yes, it really is not a nice fix, but it was a fix with minimal impact > on other parts of our logic. The real question is why this worked without problems using ExtJS4? What changed exactly?