Hi Dalmazio,

I've just played a little bit with the gallery demo and I discovered 
that the problem is (at least for Webkit) the border itself. If you do 
not set any border at the demo it works as expected. Precisely the 
complex border as for example "inset" or "outset" are causing  the 
problem. Simple borders like "black" work without a problem.

So I think it would be the most pragmatic solution to just drop any of 
the complex borders for the gallery widget. Unfortunately I haven't the 
time now to dive deeper into this problem.

I hope this short explanation also helps you a little bit :-)

cheers,
   Alex

Dalmazio Brisinda wrote:
> Hi Alex,
> 
> Looking at the problem more closely, without this block of code, the
> boundary of the Gallery widget is not respected. For example, in the qooxdoo
> demobrowser if you select Gallery on Safari/Webkit, the thumbnails appear,
> but if you look at the bottom of the browser window, you will see that the
> images continue outside of the Gallery frame until the browser window cuts
> them off.
> 
> If I add this block of code to the html example application after the
> gallery widget has been constructed and all properties set,
> 
>       // Must be added *after* the gallery's size is set.
>         if (!qx.core.Client.isGecko()) {
>             gallery.setBorder(new qx.ui.core.Border(2, "inset", null));
>         }        
> 
> the boundaries are then respected. But something I just realized is that it
> needs to be added *after* the size of the gallery widget is set (so my
> initial statement of adding this block of code to the Gallery widget
> constructor is not correct). If this block is added before the Gallery
> widget's size is set it doesn't work. So maybe just before the gallery
> widget is added to the DOM. Then the boundary of the Gallery widget is
> respected, and scroll bars appear etc. to accomodate the many thumbnails on
> Safari/Webkit.
> 
> I don't pretend to understand why this is. But I have a hunch (could be
> wrong about this) that the classes that may play a role in all this include,
> 
> qx.bom.element.Location
> qx.bom.element.Dimension
> qx.bom.element.Style
> 
> Thoughts?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to