OK, I am not really sure what goes on, but we had this problem before. I
believe that the basiskom team are the ones responsible for the QtWebKit
module delivery into PR1.2, but I see that you have already cc'ed Bruno.
Kenneth
On Mon, Apr 9, 2012 at 7:46 PM, Felipe Crochik fel...@crochik.com
Yes, it looks like a valid issue to me. When the view enters this
infinite loop, what's the size diff you see on each resize? Wondering
if removing the border:2px makes any difference.
Zalan.
On Mon, Apr 9, 2012 at 7:46 PM, Felipe Crochik fel...@crochik.com wrote:
UPDATE:
I tested the
Updates:
* noamr status: cleaning up issues with graphics surfaces, unbreaking n9
rendering
* bbandix status: fixed some compiler issues after the eastern sytem update,
now polishing gesture recognizer refactoring patch
* ahf status Finishing off my pre-easter patches :-)
* kennet
In this case it is not just the border but also the padding on body.
Removing those would probably avoid the endless loop but that is exactly
the point, we should be able to handle content that will try to be larger
than the window so the user will have to use the scroll bar. A good
example is
LD_LIBRARY_PATH is probably taking a back seat to the rpath set in your binary.
I would recommend taking QT+=webkit out of your .pro file and manually
adding the include paths and linker flags, so that you can specify the
rpath linker flag explicitly to a different path.
/s/ Adam
On Wed, Apr
