

The scrollbars will only show up if there is content that actually breaks out of the element. autoĪuto overflow is very similar to the scroll value, only it solves the problem of getting scrollbars when you don’t need them. Note: In OS X Lion, when scrollbars are set to only show when being used, scroll behaves more like auto, in that only needed scrollbars will show up. IOS’ momentum scrolling can be enabled for this value with -webkit-overflow-scrolling. Of note with this value is that you get BOTH horizontal and vertical scrollbars no matter what, even if the content requires only one or the other. Setting the overflow value of a box to scroll will hide the content from rendering outside the box, but will offer scrollbars to scroll the interior of the box to view the content. So for example a user has their default font size set larger than you would expect, you may be pushing text outside of a box and hiding it completely from their view. However, bear in mind that content that is hidden in this way is utterly inaccessible (short of viewing the source). This is particularly useful in use with dynamic content and the possibility of an overflow causing serious layout problems. This literally hides any content that extends beyond the box. The opposite of the default visible is hidden. Generally, you shouldn’t be setting static heights on boxes with web text in them anyway, so it shouldn’t come up. The important thing to remember here is that even though the content is visible outside of the box, that content does not affect the flow of the page. So in general, there is no reason to explicitly set this property to visible unless you are overriding it from being set elsewhere. If you don’t set the overflow property at all, the default is visible. Overflow comes into play more commonly when explicit widths and heights are set and it would be undesirable for any content to spill out, or when scrolling is explicitly being avoided. Unless a height is set, text will just push an element taller as well. Remember that text will naturally wrap at the end of an element (unless white-space is changed) so text will rarely be the cause of overflow.

To disable scrolling, set the scrollable option to false. However, to achieve a maximum level of accessibility through assistive technologies, disable the scrolling feature of the Grid. For more information, refer to the article on on virtual scrolling. The following example demonstrates the HTML output in a Grid with virtual scrolling. The two tables are important when you need to manually make JavaScript or CSS updates to the Grid tables.

When scrolling is enabled, the component renders two tables by default-one for the header area and one for the scrollable data area. For more information, refer to the following articles: Depending on the enabled scroll mode, the rendering of the dimensions and layout of the Grid varies.
