I have not been able to reproduce it outside of my app. I will try tomorrow
to create the scenario again, this time going overboard in my container
levels, as I think that may be where the issue is. Our app pushes qooxdoo
more then I think most apps do, and this might be where I am having a couple
Hi Jim,
On Monday 24 October 2011 22:58:34 Jim Hunter wrote:
> Nothing from the qooxdoo core team on this? It's really keeping me from
> closing a bug on my end. I was not able to get a scenario working in the
> demobrowser for this. But there should be no reason that, at any time, I
> couldn't us
Nothing from the qooxdoo core team on this? It's really keeping me from
closing a bug on my end. I was not able to get a scenario working in the
demobrowser for this. But there should be no reason that, at any time, I
couldn't use getContentLocation() and get the absolute XY coordinates of an
objec
Recently (I am using 1.2 version, but the behavior exhibits in 1.5 as well),
when I use getContentLocation() I am getting the wrong value for the Top.
What it appears is going on is that it is calculating the value based on the
accumulated height of items above it. But the problem is that one of th
