Shindig takes the approach of shifting render space management of the gadget contents to the gadget. The container may or may not support increasing or decreasing available gadget space through apis like dynamic-height and dynamic-width. It also may choose to ignore the amount of space requested by the gadget's view in the view declaration.
In new versions of shindig (and particular for html5 type gadgets) css is injected into the gadget that sets html and body tags to width:100%, height:100% and scrolling:auto. Not sure if any of this is really impacting your gadget though, since it looks like you're probably styling your main content to use the full width of the gadget. It may be that your css is using margins (instead of padding), setting width to 100%, and therefore pushing the elements beyond the available space. I'd recommend using padding (if you're not already), and box-sizing:border-box; so that padding will not extend the actual element width beyond the specified width (100%). On Wed, Sep 18, 2013 at 11:33 AM, Stanton Sievers <ssiev...@apache.org>wrote: > + dev list > > Are you using dynamic height or width features in your gadget? > > Are the height and width properties set in your ModulePrefs? If so, what > are they set to and are both containers honoring those values when > rendering? > > Thanks, > -Stanton > On Sep 18, 2013 4:31 AM, "Darren Bond" <db...@globalcad.com> wrote: > > > Dear All, We have a Shindig implementation and render our gadgets on a > > page using an ASP.NET wrapper. When comparing how our gadgets render > in > > comparison with the same gadgets on iGoogle, we tend to get content > > shifting and the introduction of vertical/horizontal scrolls bars. > iGoogle > > avoids these issues somehow. A sample screenshot can be seen here > > http://download.globalcad.com/Gadget_Appearance.png Does anyone know > of > > a > > workaround? Many thanks. Darren > > >
