A developer must not use `overflow:hidden` on section wrappers. This CSS property can hide parts of the content. It can clip important elements like buttons or text.
By Pawan Nayar · from the LLOS AI Learning record
A developer must not use `overflow:hidden` on section wrappers.
This CSS property can hide parts of the content. It can clip important elements like buttons or text.
A developer should avoid `overflow:hidden` on section wrappers. This property hides content that goes outside the wrapper's box. It can cut off buttons, hints, or other important parts of a user interface. Instead, a developer should adjust the content's size. Or, a developer should make the wrapper big enough to show all content. Only use `overflow:hidden` for specific cases. These cases include canvas containers or modal windows.
A developer adds `overflow:hidden` to a section wrapper. This section contains a crossword puzzle. The 'Hint' and 'Check' buttons are at the bottom of the puzzle. Because of `overflow:hidden`, these buttons are not visible to the user. The user cannot complete the puzzle correctly.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A developer changed the size of a status area. The developer made the status area a fixed height.
A good plan for a design tool includes a detailed product document. This document describes all features.
A developer must use `position: fixed` or `position: absolute` for an overlay pane. This makes the pane float above other content.
Carousel cards should always look full. A card with only one line of text looks empty.
A developer must not use `overflow:hidden` on section wrappers. This CSS property can hide parts of the content. It can clip important elements like buttons or text.