mirror of https://github.com/vector-im/riot-web
18ef97161a
* Convert tabbedview to functional component The 'Tab' is still a class, so now it's a functional component that has a supporting class, which is maybe a bit... jarring, but I think is actually perfectly logical. * put comment back * Fix bad tab ID behaviour * Make TabbedView a controlled component This does mean the logic of keeping what tab is active is now in each container component, but for a functional component, this is a single line. It makes TabbedView simpler and the container components always know exactly what tab is being displayed rather than having to effectively keep the state separately themselves if they wanted it. Based on https://github.com/matrix-org/matrix-react-sdk/pull/12478 * Move the active tab in user settings to the dialog title Separated by a colon, as per the new design. * Update snapshots * Update a playwright test * Fix more tests / snapshots * Attempt to test all the cases of titleForTabID * More tests |
||
|---|---|---|
| .. | ||
| audio-player | ||
| composer | ||
| create-room | ||
| crypto | ||
| editing | ||
| integration-manager | ||
| invite | ||
| knock | ||
| lazy-loading | ||
| left-panel | ||
| location | ||
| login | ||
| oidc | ||
| one-to-one-chat | ||
| permalinks | ||
| polls | ||
| presence | ||
| read-receipts | ||
| register | ||
| regression-tests | ||
| release-announcement | ||
| right-panel | ||
| room | ||
| room-directory | ||
| room_options | ||
| settings | ||
| sliding-sync | ||
| spaces | ||
| spotlight | ||
| threads | ||
| timeline | ||
| toasts | ||
| update | ||
| user-menu | ||
| user-onboarding | ||
| user-view | ||
| widgets | ||
| utils.ts | ||