As a general style I'd rather see wrapping than overflow with a scroll bar, as intentional though as it's not really possible/easy/default sometimes with HTML. That mean more work on those building pages though....

Any other thoughts from others on the general preferred approach?

-David


On Jan 2, 2008, at 1:53 PM, Adrian Crum wrote:

Marco,

It would be best to use the overflow attribute on a case-by-case basis. Adding it to the screenlet or screenlet-body styles throws off the layout on screens that don't need it.

In other words, create a style for the particular element, then apply that style to the element. Small "fixup" styles like that can be used inline - see the Webtools main.ftl file for an example. Or for screen widgets, you can create a component-specific style sheet - see the Party Manager partymgr.css file.

-Adrian

[EMAIL PROTECTED] wrote:

What about insert into main.css for the property screenlet-body the overflow auto, so in this case we will have the horizontal scrolling in case the content inside a screenlet-body overflow horizontally the screen. For example into the Store-> Shipping Estimated the table goes outside the screen and it cause a ugly effect, instead put on the css the overflow it will not happen.
What did you think of this change ?
Thanks
Marco


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to