ScrollArea
A bounded scroll container with its own scrollbar, thinner than the page’s and revealed on hover (the thumb appears when you hover or focus inside). You bound it with a maximum height or width (data-ts-max-height, data-ts-max-width). It’s what long panels use internally.
Layout · TaishoDS Core, in plain HTML.
Examples
One working example per case. Each example is the HTML of its preview—copy it as is, and with Core’s CSS and JS loaded, it looks and works the same.
Scrollable activity log
Ana Torres deployed “Dashboard” to Production.
Bruno Díaz canceled a “Marketing site” deployment.
Carla Ruiz approved the “Payments API” changes.
Diego Sosa moved “Mobile app” to Staging.
Elena Vega invited a new member as Viewer.
The “Data pipeline” deployment is queued.
When to use
- An area needs to scroll on its own without dragging the page along, like a list or a panel.
- The content is taller than the available space, and you want to bound it, not truncate it.
- You want the same thin scrollbar the system’s panels use.
When not to use
- It’s the scroll of the whole page. Leave that to the browser.
- The content fits. A scrollbar that never appears only gets in the way.
Do
- Bound it with a maximum height (
data-ts-max-height) instead of a fixed height. It adapts better. - Make it visible that there’s more below—a clean cut looks like the end of the content.
Don’t
- Don’t nest scroll areas. The user never knows which one they’re moving.
- Don’t hide important actions in it where they end up out of view.
TaishoDS Core
Needs Core’s JS, which hooks in through data-ts-* attributes.
The maximum height or width is a continuous value. --ts-scroll-area-max-h and --ts-scroll-area-max-w read it, and Core writes those variables. Until Core runs, only the scale values (ts max-h-160) and 100% are capped, because they have their own class. Any other value stays uncapped.
Core hooks into it through these attributes. They go in the markup, and there’s nothing to initialize.
data-ts-max-height
What it does: Pass the CSS length (180px, 30rem) in data-ts-max-height or data-ts-max-width. Core copies it to the variable on init and whenever the attribute changes. Scrolling is the browser’s native scrolling.
From the CDN, without a build, load taisho.scroll-area.css along with taisho.base.css. That file is all you need.
For how Core works in general, see Behavior.
Accessibility
- The scrollable container gets
tabindex="0"so it’s reachable by keyboard (axe rulescrollable-region-focusable).
Verification
What was actually tested. Anything that wasn’t tested says so—we’d rather say “not verified” than claim too much.
- axe WCAG 2.2 A + AA in a real browser, in light and dark mode, before every release.
- keyboard Adds no keys of its own—it uses the browser’s native behavior.
- screen reader Not verified with a screen reader. Test it in your own combination of components, not just here, where each one appears alone and on its happy path.