Requirements
- The tabs overview should not suddenly scroll when a tab towards the top is closed
- After the current tab is closed, the current tab should become the tab right before your current tab in the stack, not the most recent tab opened
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T157364 [FEATURE REQUEST] Tabbed Browsing | ||
| Resolved | HNordeenWMF | T384758 [Epic] Add Tabbed Browsing to the iOS App (Tabs) | |||
| Resolved | HNordeenWMF | T390916 [Sub-Epic] Tabbed Browsing V1 Main Flow & Actions | |||
| Open | None | T396157 [Sub-epic] Tabs Clean-up & Improvements | |||
| Invalid | BUG REPORT | None | T396159 Current tab should default to previous tab in stack after close, not most recently opened |
Event Timeline
Comment Actions
@HNordeenWMF I investigated on Safari and here's the behavior:
let's say you have tabs A, B, C, and D open in that order. you are on tab B --> you go to the tabs view --> you close tab B, the tab you're currently on --> there is no jumping because tab C, the next tab after the one you were previously on, becomes the tab you are now on.
can we mirror our behavior in-app to reflect this Safari protocol?
Comment Actions
@SChekfa-WMF I agree we should match safari, but we can't tell if they're jumping to A or C really can we? I think current tab becoming A makes more sense, because it works still if the current tab is the last tab. After the current tab is closed, the current tab should become the tab right before your current tab in the stack, not the most recent tab opened.