fix: preserve scroll position when switching tabs in settings

[DC-Dancao]

Description

This PR implements independent scroll positions for each tab within the settings view, enhancing user experience. Previously, the scroll position was shared across all tabs, causing incorrect scrollbar behavior when switching between tabs of different lengths. Now, the view remembers each tab's scroll position, restoring it when the user navigates back.

Changes

• src/components/Tab.tsx: Enabled ref forwarding for the TabContent component to allow parent access.

• src/views/SettingsView.tsx: Implemented logic to save and restore individual scroll positions when switching tabs.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

---

Important

Implements independent scroll positions for each tab in settings, enhancing user experience by restoring positions when switching tabs.

• Behavior:
  • Implements independent scroll positions for each tab in SettingsView.tsx, restoring them when switching tabs.
  • Previously, scroll position was shared across tabs, causing incorrect behavior.
• Components:
  • Enables ref forwarding in TabContent in Tab.tsx to allow parent access.
  • Uses useRef and useEffect in SettingsView.tsx to manage scroll positions.
• Functions:
  • handleTabChange and useEffect in SettingsView.tsx updated to save and restore scroll positions.

^{This description was created by for ad07bf4. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for your contribution! I've reviewed the changes and found that the implementation successfully addresses the scroll position preservation issue. However, there are a few suggestions that could improve the code quality and maintainability.

[roomote]

The forwardRef component should have a display name for better debugging and React DevTools support. Consider adding:

Suggested change

	})
	TabContent.displayName = 'TabContent'

right after the component definition.

[roomote]

Consider using a more descriptive variable name like tabContentScrollRef instead of contentRef to better indicate its specific purpose of tracking scroll positions.

[roomote]

The scroll positions are stored indefinitely in the ref. While not critical for a small number of tabs, consider if any cleanup is needed when the component unmounts to prevent potential memory leaks in long-running sessions.

[roomote]

Consider adding test coverage for the scroll position preservation functionality. The PR checklist indicates "Testing" is unchecked. Adding tests would help ensure this feature works correctly and prevent regressions. You could test:

• Scroll position is saved when switching tabs
• Scroll position is restored when returning to a tab
• Initial scroll position is 0 for unvisited tabs

[daniel-lxs]

Thank you @DC-Dancao!