palantir/blueprint

Support for lazy loading tabs

Open

#4,669 opened on Apr 22, 2021

View on GitHub
 (0 comments) (3 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P2Package: coreType: feature requesthelp wanted

Description

There is support for renderActiveTabPanelOnly but not something in between: Do not unmount any tabs, but only mount tabs after they are clicked on instead of all at initial load.

This is the default behavior in some libraries (eg. https://ant.design/components/tabs/, it can still overwrite default behavior with forceRender prop).

Contributor guide

Tech stack
reacttypescript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React knowledgeBlueprint tabs componentlazy loading patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests a new prop for lazy loading tabs, building on the existing `renderActiveTabPanelOnly` prop. The implementer should examine the Tabs component source code in `src/components/tabs` to understand the current rendering logic. A possible approach is to use React's `useState` and `useEffect` to mount tab panels only upon first activation. The behavior should mimic the default in Ant Design's Tabs component, with an optional `forceRender` prop. No linked PRs or comments exist, so the implementer can propose a solution in a new PR.
Support for lazy loading tabs · palantir/blueprint#4669 | Good First Issue