A hamburger menu must close when a user selects an item. In-page links must scroll smoothly with a header offset. Cross-page links must open in a new tab.
By Pawan Nayar · from the LLOS AI Learning record
A hamburger menu must close when a user selects an item.
In-page links must scroll smoothly with a header offset. Cross-page links must open in a new tab.
When a user taps a menu item, the menu must close right away. This happens before the page moves or loads. A menu that stays open feels broken to the user. Links that go to a different part of the same page must scroll smoothly. The scroll should take about 1.6 seconds. The page must stop scrolling so the sticky header does not cover the section title. Links that go to a different page must open in a new browser tab. The original page must stay open. This lets the user explore new content without losing their place on the first page.
A developer creates a website with a hamburger menu. A user clicks an item in the menu. The menu stays open while the page scrolls. The user feels confused because the menu blocks part of the screen. The developer then fixes the menu to close immediately on selection.
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 must design carousels with fixed sizes. The longest content slide sets the total height.
A developer must use plain language and avoid technical jargon. This applies to all communication and code comments.
A developer must use `position: fixed` or `position: absolute` for an overlay pane. This makes the pane float above other content.
A developer should use this navigation for articles or pages with 6 to 12 named sections. The user can quickly go to any section without getting lost.
A hamburger menu must close when a user selects an item. In-page links must scroll smoothly with a header offset. Cross-page links must open in a new tab.