mozilla-mobile/firefox-ios

"Open in Private Tab" unavailable from context menu on fresh installation

Open

#32148 opened on Feb 17, 2026

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Swift (12,950 stars) (3,203 forks)batch import
Bug 🐞Contributor OKGood first issue

Description

Steps to reproduce

  1. Erase all content and settings from iPad/iPhone simulator. (MUST DO THIS)
  2. Go to Settings :arrow_right: Homepage. Enable "Jump Back In".
  3. Open example.com on a new tab.
  4. Long press "More information...."

XCUITest: JumpBackInTests/testLongTapOnJumpBackInLink

Expected behavior

"Open in Private Tab" is available.

width=200,height=183

Actual behavior

No "Open in Private Tab" shown in the context menu.

width=200,height=183

Device & build information

  • Device: iPad simulator iOS 26.2
  • Build version: ?
  • First seen version: ?

*# *## Notes < !--- Screenshots or screen recordings are very helpful for reproducing|width=200,height=183! --> Workaround: The item becomes available from the context menu when the same test is run again.

:information_source: Reference Person

@FilippoZazzeroni

┆Issue is synchronized with this Jira Task

Contributor guide

Tech stack
swiftios
Domain
mobile
Issue type
bug
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
SwiftiOS development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The 'Open in Private Tab' option is missing from the context menu when jumping back in on a fresh iPad simulator. The issue is reproduced via the test `JumpBackInTests/testLongTapOnJumpBackInLink`. Investigate the context menu configuration logic, likely in the browser view controller or the jump back in section, to determine why the private tab option is not shown on first launch. The workaround (running the test again) suggests a state initialization race condition. Check for any flags or data that are loaded asynchronously and might not be ready on first launch. Look at the `LongPressGestureHandler` or similar classes that build the context menu, and verify the condition that adds the 'Open in Private Tab' action.