http://wikisend.com/download/971956/example.zip <http://wikisend.com/download/971956/example.zip>
^^^ this is an example of application with issue I wanted to discuss. Just open source/index.html to see what I mean. In latest Chrome 32 and Opera 18 images are not shown at all. In IE10 images are there but the list scrolling is completely broken and ugly huge scrollbar is shown on the right side. Obviously there are ways to create layouts like ones I want to have - like always it's messing with CSS margins etc. But isn't it the whole point of frameworks - you use things that were earlier implemented by other people and everything just work. If qooxdoo developers and contributors want their framework to be popular, such basic things should work out of the box... I obviously expect problems with complicated scenarios, but not in simple usecases like this one. slah, I don't really get what is that rich property. As per documentation qx.ui.mobile.basic.Atom has no property called 'rich'. -- View this message in context: http://qooxdoo.678.n2.nabble.com/HBox-layout-issues-tp7585197p7585204.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
