ionic-team / ionic-team/ionic-framework

feat: Configurable Tab History Behavior

オープン
#31,238 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
triage
主要言語
TypeScript
スター
52.7k
フォーク
13.3k
平均マージ
1日 15時間
マージ済み PR(30日)
51

説明

### Prerequisites

- [x] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#creating-an-issue).
- [x] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [x] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already include this feature request, without success.

### Describe the Feature Request

Currently, every IonTabButton press is added to the history stack. Repeatedly switching between tabs results in back navigation replaying every tab switch:

Practice → Patterns → Progress → Patterns → Progress

Back:

Progress ← Patterns ← Progress ← Patterns ← Practice

Would it be possible to support a configurable tab history mode (e.g. all, unique, or isolated) so developers can achieve navigation behavior similar to apps like Reddit, Instagram, or YouTube?

Ideally, repeated visits to the same tab would not create duplicate history entries.

### Describe the Use Case

`IonTabs` currently adds every tab switch to the history stack. Repeatedly switching between tabs causes the Android back button to replay every tab selection, leading to a ping-pong effect between tabs. This can feel unintuitive for apps that prefer Reddit/Instagram-style navigation.

### Describe Preferred Solution

Add an optional tab history mode that prevents duplicate tab visits from being added to the history stack. For example, after:

`Practice → Patterns → Progress → Patterns → Progress`

pressing Back could navigate:

`Progress ← Patterns ← Practice`

instead of replaying every tab switch.

### Describe Alternatives

_No response_

### Related Code

_No response_

### Additional Information

_No response_

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

Start with the IonTabs and IonTabButton navigation behavior described in the issue, then trace how tab presses enter the history stack. Clarify the semantics of the proposed all, unique, and isolated modes before changing behavior; done means the selected mode is configurable and repeated tab visits produce the expected Back navigation.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
typescript
領域
frontend, mobile
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
45/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。